High Rate Packet Data (HRPD) Idle State Handout From Femto Access Point to Macro Access Network

ABSTRACT

Systems and methods for identifying an address of a femto node during handoff of an access terminal from a femto node to a macro node. In one embodiment, the femto node assigns a unique identifier to the access terminal. The access terminal passes the unique identifier to the macro node. The macro node partitions the unique identifier to determine the address of the femto node. In another embodiment, the femto node registers its address with a domain name system. The macro node queries the domain name system to obtain the address of the femto node. In another embodiment, the macro node sends the unique identifier to a proxy. The proxy partitions the unique identifier to determine the address of the femto node.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present Application for Patent claims priority to ProvisionalApplication No. 61/152,589 entitled “High Rate Packet Data (HRPD) IdleState Handout From Femto to Macro Access Network” filed Feb. 13, 2009,and assigned to the assignee hereof and hereby expressly incorporated byreference herein.

REFERENCE TO CO-PENDING APPLICATIONS FOR PATENT

The present Application for Patent is related to the followingco-pending U.S. patent applications:

“High Rate Packet Data (HRPD) Idle State Handout From Femto Access Pointto Macro Access Network” having Attorney Docket No. 091310U1, filedconcurrently herewith, assigned to the assignee hereof, and expresslyincorporated by reference herein.

“High Rate Packet Data (HRPD) Idle State Handout From Femto Access Pointto Macro Access Network” having Attorney Docket No. 091310U3, filedconcurrently herewith, assigned to the assignee hereof, and expresslyincorporated by reference herein.

I. BACKGROUND

A. Field

The present application relates generally to wireless communication, andmore specifically to systems and methods to enable handoffs of idle datasessions from femto nodes to macro nodes.

B. Background

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, data, and so on. Thesesystems may be multiple-access systems capable of supportingcommunication with multiple users by sharing the available systemresources (e.g., bandwidth and transmit power). Examples of suchmultiple-access systems include code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, 3GPP Long Term Evolution (LTE)systems, and orthogonal frequency division multiple access (OFDMA)systems.

Generally, a wireless multiple-access communication system cansimultaneously support communication for multiple wireless terminals.Each terminal communicates with one or more base stations viatransmissions on the forward and reverse links. The forward link (ordownlink) refers to the communication link from the base stations to theterminals, and the reverse link (or uplink) refers to the communicationlink from the terminals to the base stations. This communication linkmay be established via a single-in-single-out, multiple-in-signal-out ora multiple-in-multiple-out (MIMO) system.

In addition to mobile phone networks currently in place, a new class ofsmall base stations has emerged, which may be installed in a user's homeand provide indoor wireless coverage to mobile units using existingbroadband Internet connections. Such personal miniature base stationsare generally known as access point base stations, or, alternatively,Home Node B (HNB) or femto cells. Typically, such miniature basestations are connected to the Internet and the mobile operator's networkvia DSL router or cable modem.

II. SUMMARY

In an embodiment, a method of identifying an address is provided. Themethod comprises receiving a first and second identifier from an accessterminal. The method further comprises generating a domain name based,at least in part, upon the first and second identifiers. The methodfurther comprises transmitting a domain name server query using thedomain name. The method further comprises receiving the address of asource access node in response to the domain name server query.

In another embodiment, a method of registering an address is provided.The method comprises assigning a first and second identifier to anaccess terminal. The method further comprises generating a domain namebased, at least in part, upon the first and second identifiers. Themethod further comprises obtaining the address of a source access node.The method further comprises transmitting a domain name serverregistration using the domain name and the address of the source accessnode.

In another embodiment, an apparatus capable of identifying an address isprovided. The apparatus comprises a processor configured to receive afirst and second identifier from an access terminal. The processor isfurther configured to generate a domain name based, at least in part,upon the first and second identifiers. The processor is furtherconfigured to transmit a domain name server query using the domain name.The processor is further configured to receive the address of a sourceaccess node in response to the domain name server query.

In another embodiment, an apparatus capable of registering an address isprovided. The apparatus comprises a processor configured to assign afirst and second identifier to an access terminal. The processor isfurther configured to generate a domain name based, at least in part,upon the first and second identifiers. The processor is furtherconfigured to obtain the address of a source access node. The processoris further configured to transmit a domain name server registrationusing the domain name and the address of the source access node.

In another embodiment, an apparatus capable of identifying an address isprovided. The apparatus comprises means for receiving a first and secondidentifier from an access terminal. The apparatus further comprisesmeans for generating a domain name based, at least in part, upon thefirst and second identifiers. The apparatus further comprises means fortransmitting a domain name server query using the domain name. Theapparatus further comprises means for receiving the address of a sourceaccess node in response to the domain name server query.

In another embodiment, an apparatus capable of registering an address isprovided. The apparatus comprises means for assigning a first and secondidentifier to an access terminal. The apparatus further comprises meansfor generating a domain name based, at least in part, upon the first andsecond identifiers. The apparatus further comprises means for obtainingthe address of a source access node. The apparatus further comprisesmeans for transmitting a domain name server registration using thedomain name and the address of the source access node.

In another embodiment, a computer program product is provided. Thecomputer program product comprises a computer readable medium. Thecomputer readable medium comprises code capable of causing at least onecomputer to receive a first and second identifier from an accessterminal. The computer readable medium further comprises code capable ofcausing at least one computer to generate a domain name based, at leastin part, upon the first and second identifiers. The computer readablemedium further comprises code capable of causing at least one computerto transmit a domain name server query using the domain name. Thecomputer readable medium further comprises code capable of causing atleast one computer to receive the address of a source access node inresponse to the domain name server query.

In another embodiment, a computer program product is provided. Thecomputer program product comprises a computer readable medium. Thecomputer readable medium comprises code capable of causing at least onecomputer to assign a first and second identifier to an access terminal.The computer readable medium further comprises code capable of causingat least one computer to generate a domain name based, at least in part,upon the first and second identifiers. The computer readable mediumfurther comprises code capable of causing at least one computer toobtain the address of a source access node. The computer readable mediumfurther comprises code capable of causing at least one computer totransmit a domain name server registration using the domain name and theaddress of the source access node.

III. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary multiple access wireless communicationsystem.

FIG. 2 illustrates a block diagram of an exemplary communication system.

FIG. 3 illustrates an exemplary wireless communication network.

FIG. 4 illustrates exemplary interoperations of two or morecommunication networks.

FIG. 5 illustrates an exemplary identifier assignment scheme used by asource node shown in FIG. 4.

FIG. 6 illustrates an exemplary data session transfer sequence.

FIG. 7 illustrates an exemplary communication system to enabledeployment of access point base stations within a network environment.

FIG. 8 illustrates exemplary interoperations of two or morecommunication networks.

FIG. 9A illustrates an exemplary identifier assignment scheme used by afemto node shown in FIG. 8.

FIG. 9B illustrates an exemplary identifier assignment scheme used by amacro node shown in FIG. 8.

FIG. 10 is a flowchart of an exemplary process for identifying anaddress of a source node shown in FIG. 8.

FIG. 11 is a flowchart of an exemplary process for performing a handofffrom a source node to a target node shown in FIG. 8.

FIG. 12 is a functional block diagram of an exemplary femto node shownin FIG. 8.

FIG. 13 is a functional block diagram of an exemplary access terminalshown in FIG. 8.

FIG. 14 is a functional block diagram of an exemplary macro node shownin FIG. 8.

FIG. 15 is a functional block diagram of an exemplary femto gatewayshown in FIG. 8.

FIG. 16 is a functional block diagram of an exemplary security gatewayshown in FIG. 8.

FIG. 17 illustrates exemplary interoperations of two or morecommunication networks implementing a domain name system.

FIG. 18 is a flowchart of an exemplary process for registering anaddress of a source node shown in FIG. 17.

FIG. 19 is a functional block diagram of an exemplary domain name systemshown in FIG. 17.

FIG. 20 is a flowchart of an exemplary process for identifying anaddress of a source node shown in FIG. 17.

FIG. 21 illustrates exemplary interoperations of two or morecommunication networks.

FIG. 22A illustrates an exemplary identifier assignment scheme used by afemto node in a communication system including a proxy.

FIG. 22B illustrates an exemplary identifier assignment scheme used by amacro node in a communication system including proxy.

FIG. 23 is a flowchart of an exemplary process for relaying a messagefrom a target access node to a source access node by a proxy shown inFIG. 21.

FIG. 24 is a flowchart of an exemplary process for statefully relaying amessage by a proxy shown in FIG. 21.

FIG. 25 is a flowchart of an exemplary process for statefully relaying amessage from a target access node to a source access node by a proxyshown in FIG. 21.

FIG. 26 is a functional block diagram of an exemplary proxy shown inFIG. 21.

FIG. 27 is a functional block diagram of yet another exemplary macronode in FIG. 8.

FIG. 28 is a functional block diagram of yet another exemplary macronode in FIG. 17.

FIG. 29 is a functional block diagram of yet another exemplary femtonode in FIG. 17.

FIG. 30 is a functional block diagram of yet another exemplary proxy inFIG. 21.

FIG. 31 is a functional block diagram of yet another exemplary macronode in FIG. 21.

IV. DETAILED DESCRIPTION

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. The techniques described herein maybe used for various wireless communication networks such as CodeDivision Multiple Access (CDMA) networks, Time Division Multiple Access(TDMA) networks, Frequency Division Multiple Access (FDMA) networks,Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA)networks, etc. The terms “networks” and “systems” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and Low Chip Rate (LCR). cdma2000 covers IS-2000,IS-95 and IS-856 standards. A TDMA network may implement a radiotechnology such as Global System for Mobile Communications (GSM). AnOFDMA network may implement a radio technology such as Evolved UTRA(E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM, etc. UTRA,E-UTRA, and GSM are part of Universal Mobile Telecommunication System(UMTS). Long Term Evolution (LTE) is an upcoming release of UMTS thatuses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documentsfrom an organization named “3rd Generation Partnership Project” (3GPP).cdma2000 is described in documents from an organization named “3rdGeneration Partnership Project 2” (3GPP2). These various radiotechnologies and standards are known in the art. For clarity, certainaspects of the techniques are described below for LTE, and LTEterminology is used in much of the description below.

Single carrier frequency division multiple access (SC-FDMA), whichutilizes single carrier modulation and frequency domain equalization isa technique. SC-FDMA has similar performance and essentially the sameoverall complexity as those of OFDMA system. SC-FDMA signal has lowerpeak-to-average power ratio (PAPR) because of its inherent singlecarrier structure. SC-FDMA has drawn great attention, especially in theuplink communications where lower PAPR greatly benefits the mobileterminal in terms of transmit power efficiency. It is currently aworking assumption for uplink multiple access scheme in 3GPP Long TermEvolution (LTE), or Evolved UTRA.

In some aspects the teachings herein may be employed in a network thatincludes macro scale coverage (e.g., a large area cellular network suchas a 3G network, typically referred to as a macro cell network) andsmaller scale coverage (e.g., a residence-based or building-basednetwork environment). As an access terminal (AT) moves through such anetwork, the access terminal may be served in certain locations byaccess nodes (ANs) that provide macro coverage while the access terminalmay be served at other locations by access nodes that provide smallerscale coverage. In some aspects, the smaller coverage nodes may be usedto provide incremental capacity growth, in-building coverage, anddifferent services (e.g., for a more robust user experience). In thediscussion herein, a node that provides coverage over a relatively largearea may be referred to as a macro node. A node that provides coverageover a relatively small area (e.g., a residence) may be referred to as afemto node. A node that provides coverage over an area that is smallerthan a macro area and larger than a femto area may be referred to as apico node (e.g., providing coverage within a commercial building).

A cell associated with a macro node, a femto node, or a pico node may bereferred to as a macro cell, a femto cell, or a pico cell, respectively.In some implementations, each cell may be further associated with (e.g.,divided into) one or more sectors.

In various applications, other terminology may be used to reference amacro node, a femto node, or a pico node. For example, a macro node maybe configured or referred to as an access node, macro AN, macro, basestation, access point (AP), eNodeB (eNB), macro cell, and so on. Also, afemto node may be configured or referred to as a femto AN, femto, HomeNodeB (HNB), Home eNodeB (HeNB), access point (AP), femto access point(FAP), base transceiver station (BTS), femto cell, and so on. An accessterminal may also be called user equipment (UE), a wirelesscommunication device, terminal, or some other terminology.

Referring to FIG. 1, a multiple access wireless communication systemaccording to one embodiment is illustrated. An access point 100 includesmultiple antenna groups, one antenna group including antennas 104 and106, another antenna group including antennas 108 and 110, and anadditional antenna group including antennas 112 and 114.

In FIG. 1, only two antennas are shown for each antenna group, however,more or fewer antennas may be utilized for each antenna group. Accessterminal 116 is in communication with antennas 112 and 114, whereantennas 112 and 114 transmit information to access terminal 116 overforward link 120 and receive information from access terminal 116 overreverse link 118. Access terminal 122 is in communication with antennas106 and 108, where antennas 106 and 108 transmit information to accessterminal 122 over forward link 126 and receive information from accessterminal 122 over reverse link 124. In a frequency division duplex (FDD)system, communication links 118, 120, 124 and 126 may use differentfrequency for communication. For example, forward link 120 may use adifferent frequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access point. In theillustrated embodiment, antenna groups each are designed to communicateto access terminals in a sector, of the areas covered by access point100.

In communication over forward links 120 and 126, the transmittingantennas of access point 100 utilize beamforming in order to improve thesignal-to-noise ratio of forward links for the different accessterminals 116 and 124. Also, an access point using beamforming totransmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access point transmitting through a single antenna to all its accessterminals.

FIG. 2 is a block diagram of an embodiment of a transmitter system 210(also known as the access point) and a receiver system 250 (also knownas access terminal) in a MIMO system 200. At the transmitter system 210,traffic data for a number of data streams is provided from a data source212 to a transmit (TX) data processor 214.

In an embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TXMIMO processor 220, which may further process the modulation symbols(e.g., for OFDM). TX MIMO processor 220 then provides NT modulationsymbol streams to NT transmitters (TMTR) 222 a through 222 t. In certainembodiments, TX MIMO processor 220 applies beamforming weights to thesymbols of the data streams and to the antenna from which the symbol isbeing transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. NTmodulated signals from transmitters 222 a through 222 t are thentransmitted from NT antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby NR antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g., filters, amplifies, anddownconverts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the NR receivedsymbol streams from NR receivers 254 based on a particular receiverprocessing technique to provide NT “detected” symbol streams. The RXdata processor 260 then demodulates, de-interleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 260 is complementary to thatperformed by TX MIMO processor 220 and TX data processor 214 attransmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use(discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 then determines which pre-coding matrix to usefor determining the beamforming weights then processes the extractedmessage.

In an aspect, logical channels are classified into Control Channels andTraffic Channels. Logical Control Channels comprise Broadcast ControlChannel (BCCH) which is a DL channel for broadcasting system controlinformation. Paging Control Channel (PCCH) is a DL channel thattransfers paging information. Multicast Control Channel (MCCH) is aPoint-to-multipoint DL channel used for transmitting Multimedia Also, aMulticast Traffic Channel (MTCH) is a Point-to-multipoint DL channel forused for transmitting traffic data. Broadcast and Multicast Service(MBMS) scheduling and control information for one or several MTCHs.Generally, after establishing a RRC connection this channel is only usedby UEs that receive MBMS. Dedicated Control Channel (DCCH) is aPoint-to-point bi-directional channel that transmits dedicated controlinformation and used by UEs having an RRC connection. In another aspect,Logical Traffic Channels comprise a Dedicated Traffic Channel (DTCH)which is a Point-to-point bi-directional channel, dedicated to one UE,for the transfer of user information.

In another aspect, Transport Channels are classified into DL and UL. DLTransport Channels comprise a Broadcast Channel (BCH), a Downlink SharedData Channel (DL-SDCH) and a Paging Channel (PCH), the PCH for supportof UE power saving (DRX cycle is indicated by the network to the UE),broadcasted over entire cell and mapped to physical resources (PHY)which can be used for other control/traffic channels. The UL TransportChannels comprise a Random Access Channel (RACH), a Request Channel(REQCH), an Uplink Shared Data Channel (UL-SDCH) and plurality of PHYchannels. The PHY channels comprise a set of DL channels and ULchannels.

FIG. 3 illustrates an exemplary wireless communication network 300. Thewireless communication network 300 is configured to supportcommunication between multiple users. The wireless communication network300 may be divided into one or more cells 302, such as, for example,cells 302 a-302 g. Communication coverage in cells 302 a-302 g may beprovided by one or more nodes 304, such as, for example, nodes 304 a-304g. Each node 304 may provide communication coverage to a correspondingcell 302. The nodes 304 may interact with a plurality of accessterminals, such as, for example, ATs 306 a-306 l.

Each AT 306 may communicate with one or more nodes 304 on a forward link(FL) and/or a reverse link (RL) at a given moment. A FL is acommunication link from a node to an AT. A RL is a communication linkfrom an AT to a node. The nodes 304 may be interconnected, for example,by appropriate wired or wireless interfaces and may be able tocommunicate with each other. Accordingly, each AT 306 may communicatewith another AT 306 through one or more nodes 304. For example, the AT306 j may communicate with the AT 306 h as follows. The AT 306 j maycommunicate with the node 304 d. The node 304 d may then communicatewith the node 304 b. The node 304 b may then communicate with the AT 306h. Accordingly, a communication is established between the AT 306 j andthe AT 306 h.

The wireless communication network 300 may provide service over a largegeographic region. For example, the cells 302 a-302 g may cover only afew blocks within a neighborhood or several square miles in a ruralenvironment. In one embodiment, each cell may be further divided intoone or more sectors (not shown).

As described above, a node 304 may provide an access terminal 306 accesswithin its coverage area to a communications network, such as, forexample the internet or a cellular network.

An AT 306 may be a wireless communication device (e.g., a mobile phone,router, personal computer, server, etc.) used by a user to send andreceive voice or data over a communications network. As shown, ATs 306a, 306 h, and 306 j comprise routers. ATs 306 b-306 g, 306 i, 306 k, and306 l comprise mobile phones. However, each of ATs 306 a-306 l maycomprise any suitable communication device.

FIG. 4 illustrates exemplary interoperations of two or morecommunication networks within a larger communication network 400. In theillustrated embodiment, communication network 410 and communicationnetwork 415 may be generally similar to the communication network 300shown in FIG. 3. Communication network 410 may comprise one or more basetransceiver stations (BTSs), such as BTS 420 and BTS 425. BTS 420 andBTS 425 may communicate with one or more ATs, such as AT 430 and AT 435.In the illustrated embodiment, BTSs 420 and 425 may be generally similarto access point 100 shown in FIG. 1, and ATs 430 and 435 may includeMIMO system 200 shown in FIG. 2. Similarly, communication network 415may comprise one or more BTSs, such as BTS 440 and BTS 445. BTS 440 andBTS 445 may communicate with one or more ATs, such as AT 450 and AT 455.In the illustrated embodiment, BTSs 440 and 445 may be generally similarto access point 100 shown in FIG. 1, and ATs 450 and 455 may includeMIMO system 200 shown in FIG. 2. In an embodiment, a base stationcontroller (BSC) 470 may control communication network 410, and BSC 475may control communication network 415. BSC 470 and BSC 475 maycommunicate via a network interface to facilitate inter-networkoperations. An example of such interface is A13 interface 480. In someembodiments, a radio network controller (RNC) (not shown) may facilitateinter-network operations. The RNC may be generally similar to a BSC.

In an embodiment, an AT may initiate communication with a BTS.Communication may comprise voice and/or data-only information(collectively referred to herein as “data”). For example, AT 435 mayinitiate a data session with BTS 425. BTS 425 may assign AT 435 one ormore identifiers, such as a unicast access terminal identifier (UATI)and a color code. BTS 425 may assign AT 435 a UATI via a UATI assignmentmessage.

The UATI may uniquely identify the AT 435 within the largercommunication network 400. The UATI may also identify the base station,BTS 425, with which AT 435 is in communication. In some embodiments, theUATI may identify the BSC 470 via a BSC_ID. The BSC_ID may be logicallydivided into one or more most significant bits (MSB) and one or moreleast significant bits (LSB). The one or more MSBs of the BSC_ID may bereferred to as an upper BSC_ID or a BSC_ID_MSB, and the one or more LSBsof the BSC_ID may be referred to as a lower BSC_ID or BSC_ID_LSB. Insome embodiments, the UATI is 128 bits long (collectively referred to asa UATI128). The UATI may be logically divided into one or more mostsignificant bits (MSB) and one or more least significant bits (LSB). Theone or more MSBs of the UATI may be referred to as an upper UATI, andthe one or more LSBs of the UATI may be referred to as a lower UATI. Inan embodiment, the upper UATI may comprise the 104 most significant bitsof the UATI128, collectively referred to as a UATI104. In an embodiment,the lower UATI may comprise the 24 least significant bits of theUATI128, collectively referred to as a UATI24.

The color code may partially identify the BSC 470 and may uniquely mapto one or more bits of the upper UATI. In some embodiments, the colorcode may be 8 bits long. In some embodiments, the color code may bemapped to the upper UATI on a one-to-one basis. Thus, in the examplewhere an 8-bit color code maps to a 104-bit upper UATI (UATI104), only256 different values of the UATI104 are valid. In an embodiment, thecolor code is provided to the AT 435 by the BTS 425. In anotherembodiment, the UATI is provided to the AT 435 by the BTS 425 and the AT435 determines the color code from the UATI.

At some point, it may be desirable for an AT communicating with a BTS incommunication network 410 to initiate handoff to a BTS in communicationnetwork 415. For example, AT 435 may be in communication with BTS 425but detect a stronger signal from BTS 440. In an embodiment, AT 455 mayinitiate handoff from BTS 425 to BTS 440. In the illustrated example,BTS 425 may be considered a source access node, and BTS 440 may beconsidered a target access node. Similarly, communication network 410may be called a source access network, and communication network 415 maybe called a target access network.

In requesting handoff, AT 435 may send a handoff request to BTS 440,including identification information, which may include portions of theUATI and/or color code received from BTS 425. As discussed below, BTS440 may use the identification information supplied by AT 435 todetermine the address of the source node, BTS 425. In an embodiment, BSC475 receives the identification information from BTS 440 and determinesthe address of BSC 470, which controls the source access network,communication network 410. The target node, BTS 425, may transmit asession transfer request to the source node, BTS 440. Specifically, BTS425 may transmit the session transfer request through BSC 475, which maysend an A13 message 480 to BSC 470, which in turn may forward thesession transfer request to BTS 425.

FIG. 5 illustrates an exemplary identifier assignment scheme used by thesource node shown in FIG. 4. As described with respect to FIG. 4, AT 435may send a handoff request to BTS 440, including identificationinformation 500, which may be mapped to the UATI 510. In the illustratedembodiment, the identification information 500 comprises the color code520 and the lower UATI 530.

As described above, the color code 520 may uniquely map to one or morebits of the upper UATI 540. In some embodiments, the upper UATI 540 maybe 104 bits long, and may be referred to as the UATI104. In someembodiments, the upper UATI 540 may include the BSC_ID_MSB 550. TheBSC_ID_MSB 550 may comprise one or more bits of the upper UATI 540. Inthe illustrated embodiment, the BSC_ID_MSB 550 comprises one or more ofthe least significant bits of the upper UATI 540.

In some embodiments, the lower UATI 530 may be 24 bits long, and may bereferred to as the UATI24. The lower UATI 530 may include the BSC_ID_LSB560 and an AT-specific identifier (ATID) 570. In the illustratedembodiment, the BSC_ID_LSB comprises one or more of the most significantbits of the lower UATI 530, and the ATID 570 comprises one or more ofthe least significant bits of the lower UATI 530.

In the illustrated embodiment, the upper UATI 540 may be mapped from thecolor code 520 and combined with the lower UATI 530 to form the UATI510. Similarly, the BSC_ID_MSB may be mapped from the color code 520 andcombined with the BSC_ID_LSB to form the BSC_ID. As described withrespect to FIG. 4, these mappings may be performed by the BTS 440, BSC475, or the associated RNC (not shown).

FIG. 6 illustrates an exemplary data session transfer sequence 600,initiated by AT 610 from a source access network 620 to a target accessnetwork 630. In an embodiment, AT 610 may be generally similar to AT 435shown in FIG. 4. In an embodiment, the source access network 620 may begenerally similar to communication network 410 shown in FIG. 4. Sourceaccess network 620 may be in a first subnet, “subnet A.” In anembodiment, the target access network 630 may be generally similar tocommunication network 415 shown in FIG. 4. The target access network 630may be in a second subnet, “subnet B.”

In an exemplary step 650, AT 610 accesses the target access network 630with the color code and UATI24 previously assigned by the source accessnetwork 620. Next, in step 655, the target access network 630 constructsa source UATI (UATI_A) from the color code and UATI24 received from AT610 and determines the address of the source access network 620.Proceeding to step 660, the target access network 630 sends a sessiontransfer request to source access network 620, using the source UATI.Moving to step 665, source access network 620 sends the sessionassociated with the UATI to the target access network 630. Continuing tostep 670, the session is copied into the target access network 630.Then, in step 675, the target access network 630 assigns a new UATI(UATI_B) to the AT 610. Subsequently, in step 680, AT 610 sends amessage to the target access network 630, which confirms reception ofthe new UATI. Thereafter, in step 685, the target access network 630sends a message to the source access network 620, which confirmsreception of the session associated with the source UATI. Finally, instep 690, the source access network 620 purges the session associatedwith the source UATI.

With respect to step 655, the address of the source access network 620may be found in a lookup table. The lookup table may be indexed to colorcode, thereby associating each color code with an address.Alternatively, the lookup table may be indexed to BSC_ID, therebyassociating each BSC_ID with an address. In either embodiment, the sizeof the lookup table is correlated with the size of the color code. Invarious embodiments, the lookup table may be implemented at one or moreof the BTS, BSC, and femto gateway associated with the target accessnetwork 630.

FIG. 7 illustrates an exemplary communication system to enabledeployment of access point base stations within a network environment.As shown in FIG. 7, the system 700 includes multiple access point basestations, which may comprise access point 100 (see FIG. 1). In anembodiment, the system includes femto cells, Home Node B units, or Homeevolved Node B units, such as, for example, HNBs 710, each beinginstalled in a corresponding small scale network environment, such as,for example, in one or more user residences 730, and being configured toserve associated, as well as alien, user equipment or mobile stations720. Each HNB 710 is further coupled to the Internet 740 and a mobileoperator core network 750 via an Internet access device (not shown) suchas, for example, a DSL router or a cable modem.

FIG. 8 illustrates exemplary interoperations of two or morecommunication networks. It may desirable for an AT 820 to transmitinformation to and receive information from another AT, such as AT 821.FIG. 8 illustrates a manner in which the AT 820 may communicate with theAT 821. As shown in FIG. 8, the macro node 805 may provide communicationcoverage to access terminals within a macro area 830. For example, theAT 820 may generate and transmit a message to the macro node 805. Themessage may comprise information related to various types ofcommunication (e.g., voice, data, multimedia services, etc.). The AT 820may communicate with the macro node 805 via a wireless link.

The macro node 805 may also communicate with a femto gateway (FGW), suchas the FGW 852 operating in communication network 850. For example, themacro node 805 may transmit the message received from the AT 820 to theFGW 852. Generally, the FGW 852 may facilitate communication between theAT 820 and the AT 821 by first receiving the message received from theAT 820 via the macro node 805. The FGW 852 may then transmit the messagethrough a security gateway (SGW), such as the SGW 854, which may act asa transparent tunnel to a femto node. The macro node 805 and the FGW 852may communicate via a wired link. For example, a direct wired link maycomprise a fiber optic or Ethernet link. The macro node 805 and the FGW852 may be co-located or deployed in different locations.

The FGW 852 may also communicate with the security gateway (SGW) 854.Generally, the SGW 854 may facilitate communication between the AT 820and the AT 821 by providing a transparent tunnel from the FGW 852 to afemto node. The SGW 854 may act as a tunnel by first receiving themessage from the AT 820 via the macro node 805 and the FGW 852. The SGW854 may then relay the message to a femto node for transmission to theAT 821. The FGW 852 and the SGW 854 may communicate via a direct wiredlink as described above. The FGW 852 and the SGW 854 may be co-locatedor may be deployed in different locations.

The SGW 854 may also communicate with the Internet 840 (and/or anotherappropriate wide area network). Generally, the Internet 840 mayfacilitate communication between the AT 820 and the AT 821 by firstreceiving the message from the AT 820 via the macro node 805, the FGW852, and the SGW 854. The Internet 840 may then transmit the message toa femto node, such as the femto node 812 for transmission to the AT 821.The SGW 854 may communicate with the Internet 840 via a wired orwireless link as described above.

The Internet 840 may also communicate with femto nodes, such as thefemto nodes 810, 812. The femto node 812 may facilitate communicationbetween the AT 820 and the AT 821 by providing communication coveragefor the AT 820 within a femto area 817. For example, the femto node 812may receive the message originating at the AT 820 via the macro node805, the FGW 852, the SGW 854, and the Internet 840. The femto node 812may then transmit the message to the AT 821 in the femto area 817. Thefemto node 812 may communicate with the AT 821 via a wireless link.

As described above, the macro node 805, the FGW 852, the SGW 854, theInternet 840, and the femto node 812 may interoperate to form acommunication link between the AT 820 and the AT 821. For example, theAT 820 may generate and transmit a message to the macro node 805. Themacro node 805 may then transmit the message to the FGW 852. The FGW 852may subsequently transmit the message through the SGW 854. The SGW 854may then transparently relay the message to the Internet 840. TheInternet 840 may then transmit the message to the femto node 812. Thefemto node 812 may then transmit the message to the AT 821. Similarly,the reverse path may be followed from the AT 821 to the AT 820.

In one embodiment, the femto nodes 810, 812 may be deployed byindividual consumers and placed in homes, apartment buildings, officebuildings, and the like. The femto nodes 810, 812 may communicate withthe ATs in a predetermined range (e.g., 100 m) of the femto nodes 810,812 utilizing a predetermined cellular transmission band. In oneembodiment, the femto nodes 810, 812 may communicate with the Internet840 by way of an Internet Protocol (IP) connection, such as a digitalsubscriber line (DSL, e.g., including asymmetric DSL (ADSL), high datarate DSL (HDSL), very high speed DSL (VDSL), etc.), a TV cable carryingInternet Protocol (IP) traffic, a broadband over power line (BPL)connection, or other link. In another embodiment, the femto nodes 810,812 may communicate with the SGW 854 via a direct link.

As described above, multiple femto nodes 810, 812 may be deployed withinthe macro area 830. The deployment of multiple femto nodes 810, 812, inthe macro area 830 may make it desirable to improve the process ofhanding off a data session from the femto node 810 to the macro node805. For example, the AT 822 may initiate a data session bycommunicating with the femto node 810. After some time, the data sessionmay go idle. A data session may be said to be idle when data is notactively transferred, but the session persists. As the AT 822 moves, itmay be advantageous for the femto node 810 to hand off the call to macronode 805. In one example, the AT 822 may be located at the edge of thefemto area 815 where the coverage provided by the femto node 810 maybegin to deteriorate. However, in the same area, the coverage providedby the macro node 805 in macro area 830 may be strong. Accordingly, itmay be desirable for the macro node 805 to hand in the AT 822 from thefemto node 810. In addition to alleviating deteriorating coverage, itmay be desirable for the macro node 805 to hand in from the femto node810 for other reasons. For example, the femto node 810 may not have thecapacity to service a large number of ATs. It may be beneficial tooverall system performance to offload some of the AT communicationtraffic from the femto node 810 by handing in ATs to macro nodes.

In an embodiment, session transfer from femto node 810 to macro node 805may proceed generally as shown in FIG. 6. Specifically, the process ofhanding in from the femto node 810 to the macro node 805 may require themacro node 805 to identify the address of the femto node 810 in order tosend a session transfer request.

As discussed with respect to FIG. 6, the size of the color code maylimit the number of unique addresses available. In the context ofmacro-to-macro session transfer, this limitation may be acceptable dueto the generally large size of access network. Specifically, largeraccess networks may allow for a lower number of access networks andtherefore require fewer bits to address. Because femto nodes may berelatively small and numerous, there may not be enough bits available inthe legacy UATI assignment scheme to support all the necessary colorcodes or BSC_IDs. As additional femto nodes are deployed withinnetwork-at-large, it may be desirable to improve the manner in which theaddresses of femto nodes are identified during the hand in process.

A. UATI Assignment Differentiation

In one embodiment, access networks may adjust the UATI assignment schemedepending on whether the access network is a femto node or a macro node.FIG. 9A illustrates an exemplary identifier assignment scheme used by afemto node, such as femto node 810 shown in FIG. 8. In an embodiment,femto assignment scheme 900 may be used by femto node 810 when assigninga UATI 905 to an AT such as AT 822 (see FIG. 8). Because femto cells maycover relatively smaller areas than macro cells, they may also provideservice to a relatively small number of ATs. Therefore, in anembodiment, a femto cell may allocate relatively fewer bits of the lowerUATI 910 to the ATID 915. For example, the femto cell may allocate about4 bits to the ATID 915. In some embodiments, the femto cell may allocatebetween about 3 bits and about 5 bits to the ATID 915. In someembodiments, the femto cell may allocate between about 2 bits and about10 bits to the ATID 915. Accordingly, the femto cell may allocaterelatively more bits of the lower UATI 910 to the BSC_ID_LSB 920. Forexample, the femto cell may allocate about 20 bits to the BSC_ID_LSB920. In some embodiments, the femto cell may allocate between about 19and about 21 bits to the BSC_ID_LSB 920. In some embodiments, the femtocell may allocate between about 14 and about 22 bits to the BSC_ID_LSB920.

In the illustrated embodiment, as in FIG. 5, the upper UATI 925comprises a BSC_ID_MSB 930 mapped from the color code. In someembodiments, BSC_ID_MSB 930 is about 12 bits long. In some embodiments,BSC_ID_MSB 930 is between about 11 and about 13 bits long. In someembodiments, the BSC_ID_MSB 930 is between about 10 and about 18 bitslong. In some embodiments, the BSC_ID_MSB 930 may be longer than 104bits. Together, the BSC_ID_MSB 930 and the BSC_ID_LSB 920 may composethe BSC_ID 935. In some embodiments, BSC_ID 935 may represent the IPaddress of the femto cell. In some embodiments, the BSC_ID 935 may mapto the address of the femto cell.

FIG. 9B illustrates an exemplary identifier assignment scheme used by amacro node, such as macro node 805 shown in FIG. 8. In an embodiment,macro assignment scheme 950 may be used by macro node 805 when assigninga UATI 955 to an AT such as AT 822 (see FIG. 8). In some embodiments,macro assignment scheme 950 may comprise the assignment scheme used forUATI 510 shown in FIG. 5. Because macro cells may cover relativelylarger areas than femto cells, they may also provide service to arelatively large number of ATs. Therefore, in an embodiment, a macrocell may allocate relatively more bits of the lower UATI 960 to the ATID965. For example, the femto cell may allocate about 20 bits to the ATID965. In some embodiments, the femto cell may allocate between about 19bits and about 21 bits to the ATID 965. In some embodiments, the femtocell may allocate between about 14 bits and about 22 bits to the ATID965. Accordingly, the femto cell may allocate relatively more bits ofthe lower UATI 960 to the BSC_ID_LSB 970. For example, the femto cellmay allocate about 4 bits to the BSC_ID_LSB 970. In some embodiments,the femto cell may allocate between about 3 and about 5 bits to theBSC_ID_LSB 970. In some embodiments, the femto cell may allocate betweenabout 2 and about 10 bits to the BSC_ID_LSB 970.

In the illustrated embodiment, as in FIG. 5, the upper UATI 975comprises a BSC_ID_MSB 980 mapped from the color code. In someembodiments, BSC_ID_MSB 980 is about 28 bits long. In some embodiments,BSC_ID_MSB 980 is between about 27 and about 29 bits long. In someembodiments, the BSC_ID_MSB 980 is between about 12 and about 30 bitslong. In some embodiments, the BSC_ID_MSB 980 may be longer than 104bits. Together, the BSC_ID_MSB 980 and the BSC_ID_LSB 970 may composethe BSC_ID 985. The BSC_ID may be the IP address of the femto cell.

FIG. 10 is a flowchart of an exemplary process for identifying anaddress of a source node shown in FIG. 8. As described above withrespect to FIG. 8, the process 1000 may be used to help identify theaddress of a source node during a hand in process to a target node.

As shown in exemplary step 1010, an access terminal transmits a firstand second identifier to a target access node. In an embodiment, theaccess terminal may be AT 822 and the target access node may be macronode 805. The first identifier may comprise the color code that the AT822 previously received from the femto node 810. Alternatively, thefirst identifier may comprise one or more bits of the upper UATI thatthe AT 822 previously received from the femto node 810. The secondidentifier may comprise the lower UATI that the AT 822 previouslyreceived from the femto node 810. In an embodiment, the femto node 810may have generated a UATI and assigned the UATI to the AT 822. The AT822 may have resolved the color code from one or more bits of the UATI.In another embodiment, the femto node 810 may have transmitted the boththe color code and one or more bits of the UATI to the AT 822. The AT822 may have stored the color code and the UATI in a memory.

Next, in step 1020, the target access node receives the first and secondidentifier from the AT. In one embodiment, the macro node 805 mayreceive the color code and the lower UATI from the AT 822. The macronode 805 may store the color code and lower UATI in a memory. In oneembodiment, the macro node 805 may forward the color code and lower UATIto the FGW 852 for processing.

Continuing to step 1030, a processing element determines an access nodetype of a source access node based upon the first identifier. In anembodiment, the processing element is the macro node 805. In anotherembodiment, the processing element is FGW 852. Possible node types mayinclude macro nodes and femto nodes. The processing element may performa lookup on the first identifier in order to determine whether thesource node is a macro or femto node. In embodiments where the firstidentifier comprises the color code of the source node, one or morecolor codes may be reserved to identify the source node as a femto node.In embodiments where the first identifier comprises one or more bits ofthe upper UATI, the processing element may first map the firstidentifier to a subnet and/or BSC_ID_MSB and then compare the resultwith a list of known femto nodes.

Proceeding to step 1040, the processing element partitions the secondidentifier into a source access node code and an access terminal code.In an embodiment, the second identifier may be the lower UATI as shownin FIG. 9A and FIG. 9B. Thus, the source access node code may comprisethe BSC_ID_LSB and the access terminal code may comprise the ATID. In anembodiment, the processing element may partition the second identifieras shown in 9A and 9B. For example, if the processing element determinesthe access node to be a femto node, the processing element may extractthe BSC_ID_LSB and ATID in accordance with femto UATI assignment scheme900, shown in FIG. 9A. Alternatively, if the processing elementdetermines the access node to be a macro node, the processing elementmay extract the BSC_ID_LSB and ATID in accordance with macro UATIassignment scheme 950, shown in FIG. 9B. Thus, when the source accessnode is a femto node, the extracted BSC_ID_LSB may have more bits thanwhen the source access node is a macro node. Similarly, when the sourceaccess node is a femto node, the extracted ATID may have fewer bits thanwhen the source access node is a macro node. The processing element maystore the BSC_ID_LSB and/or ATID in a memory.

Moving to step 1050, the processing element obtains the address of thesource access node. When the source access node is a femto node, theprocessing element may map the color code to an upper UATI and extractthe BSC_ID_MSB as shown in FIG. 5. The processing element mayconcatenate the BSC_ID_MSB with the BSC_ID_LSB to form the BSC_ID. Insome embodiments, the BSC_ID of the femto access node may be the IPaddress of the source access node. When the source access node is amacro node, the processing element may simply perform a lookup on thecolor code to determine the IP address of the source access node. Insome embodiments, the processing element may map the color code to anupper UATI and extract the BSC_ID_MSB as shown in FIG. 5. The processingelement may concatenate the BSC_ID_MSB with the BSC_ID_LSB to form theBSC_ID. In some embodiments, the BSC_ID of the macro access node may bethe IP address of the source access node.

FIG. 11 is a flowchart of an exemplary process for performing a handofffrom a source node to a target node shown in FIG. 8. As described abovewith respect to FIG. 8, the process 1100 may be used to transfer a datasession from a source access node to a target access node. In oneembodiment, the source access node is femto node.

In step 1110, a processing element receives an 8-bit color code and a24-bit UATI24 from an AT. In an embodiment, the processing element maybe a macro node such as macro node 805. In another embodiment, theprocessing element may be an FGW such as FGW 852.

Next, in step 1120, the processing element maps the color code into theUATI104 as shown in FIG. 5. Then, in step 1130, the processing elementdetermines the node type of the source access node based upon the colorcode. Possible node types may include macro nodes and femto nodes. In anembodiment, some color code values may be reserved to indicate a femtosource access node. In some embodiments, one or more bits of the colorcode may act as a flag indicating a femto source access node. Atdecision point 1140, the flowchart branches depending on whether thenode type of the source access node is a femto node type or a macro nodetype.

If the source access node is a femto node, the processing elementpartitions the UATI24 accordingly in step 1150. Specifically, theprocessing element extracts a relatively longer BSC_ID_LSB and arelatively shorter ATID, as shown in FIG. 9A. Alternatively, if thesource access node is a macro node, the processing element partitionsthe UATI24 differently in step 1160. Specifically, the processingelement extracts a relatively shorter BSC_ID_LSB and a relatively longerATID, as shown in FIG. 9B.

Continuing to step 1170, the processing element obtains a 32-bit IPaddress of the source access node by combining one or more bits from theLSB of the UATI104 with the extracted BSC_ID_LSB. In some embodiments,the one or more bits from the LSB of the UATI104 may comprise theBSC_ID_MSB. Thus, the BSC_ID_MSB is combined with the BSC_ID_LSB to forthe BSC_ID, which may be the IP address of the source access node.

Proceeding to step 1180, the target access node transfers the datasession from the source access node. In some embodiments, the datasession transfer may operate as shown in FIG. 6. In an embodiment,target node 805 may transmit a session transfer request to the sourcenode 810. Specifically, macro node 805 may transmit the session transferrequest through FGW 852, which may send an A13 message through SGW 854,over the Internet 840 to femto node 810. Femto node 810 may transfer thedata session via the reverse path.

FIG. 12 is a functional block diagram of an exemplary femto node 810shown in FIG. 8. In an embodiment, as discussed above with respect toFIG. 8, the femto node 810 may facilitate a hand out from the femto node810 to the macro node 805 by providing the AT 822 with an identifiersuch as a UATI. The femto node 810 also facilitate a hand out from thefemto node 810 to the macro node 805 by transferring the data session tothe macro node 805, as shown in FIG. 4. The femto node 810 may comprisea wireless network interface 1210 configured to transmit an outboundwireless message, such as a UATI assignment message, to the AT 822. Thewireless network interface 1210 may also receive an inbound wirelessmessage from the AT 822. Wireless network interface 1210 may be coupledto a processor 1220. The processor 1220 may be configured to process theUATI assignment message and the inbound and outbound wireless messagescoming from or going to the AT 822 via the wireless network interface1210. The processor 1220 may also be configured to control othercomponents of the femto node 810. The processor 1220 may be furthercoupled to a wired network interface 1230. The wired network interface1230 may be configured to pass an outbound wired message to, and receivean inbound wired message from, the Internet 840. The wired networkinterface 1230 may pass the inbound wired message to the processor 1220for processing. The processor 1220 may process and pass the wiredoutbound message to the wired network interface 1210 for transmission.For example, the processor 1220 may be configured to process datasession transfer messages coming from or going to the macro node 805, asdescribed with respect to FIG. 6.

The processor 1220 may further be coupled, via one or more buses, to amemory 1240. The processor 1220 may read information from or writeinformation to the memory 1240. For example, the memory 1240 may beconfigured to store inbound or outbound messages before, during, orafter processing. In particular, the memory 1240 may be configured tostore the UATI assignment message and/or data session transfer messages.The processor 1220 may also be coupled to a message formatter 1250. Themessage formatter 1250 may be configured to generate the UATI assignmentmessage used to facilitate a hand out from the femto node 810 to themacro node 805. As described above with respect to FIG. 9A, the UATIassignment message may comprise one or more of a color code, femtoBSC_ID, and ATID. The message formatter 1250 may pass the generated UATIassignment message to processor 1220 for any additional processingbefore the UATI assignment message is transmitted via the wirelessnetwork interface 1210 to AT 822. The message formatter 1250 may also becoupled directly to the memory 1240 in order to store or retrieveinformation for use in message formatting.

The wireless network interface 1210 may comprise an antenna and atransceiver. The transceiver may be configured to modulate/demodulatethe wireless outbound/inbound messages going to or coming from AT 822respectively. The wireless outbound/inbound messages may betransmitted/received via the antenna. The antenna may be configured tosend and/or receive the outbound/inbound wireless messages to/from theAT 822 over one or more channels. The outbound/inbound messages maycomprise voice and/or data-only information (collectively referred toherein as “data”). The wireless network interface 1210 may demodulatethe data received. The wireless network interface 1210 may modulate datato be sent from the femto node 810 via the wireless network interface1210. The processor 1220 may provide data to be transmitted.

The wired network interface 1230 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound wired messagesgoing to or coming from the Internet 840. The wired network interface1230 may demodulate data received. The demodulated data may betransmitted to the processor 1220. The wired network interface 1230 maymodulate data to be sent from the femto node 810 via the wired networkinterface 1230. The processor 1220 may provide data to be transmitted.

The memory 1240 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1240 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the femto node 810 need not be separatestructural elements. For example, the processor 1220 and the memory 1240may be embodied in a single chip. The processor 1220 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the femto node 810, suchas processor 1220 and message formatter 1250, may be embodied as ageneral purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any suitablecombination thereof designed to perform the functions described herein.One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the femto node 810 mayalso be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcommunication, or any other such configuration.

FIG. 13 is a functional block diagram of an exemplary access terminal822 shown in FIG. 8. As discussed above, the AT 822 may be a mobilephone. The AT 822 may be used to facilitate a hand out from the femtonode 810 to the macro node 805 by receiving a UATI from the femto node810 and passing the identifying information in the UATI to the macronode 805.

The AT 822 may comprise a processor 1305 configured to processinformation for storage, transmission, and/or for the control of othercomponents of the AT 822. The processor 1305 may further be coupled to amemory 1310. The processor may read information from or writeinformation to the memory 1310. The memory 1310 may be configured tostore messages before, during or after processing. In particular, thememory 1310 may be configured to store the UATI and the accompanyingidentifying information. The processor 1305 may also be coupled to awireless network interface 1315. The wireless network interface 1315 maybe configured to receive and inbound wireless message from, and transmitan outbound wireless message to the femto node 810 or the macro node805. The inbound wireless message may be passed to the processor 1305for processing. The processor 1305 may process the outbound wirelessmessage passing the outbound wireless message to the wireless networkinterface 1315 for transmission.

The processor 1305 may also be coupled to a message interpreter 1320.The inbound wireless message received at the wireless network interface1315 from the femto node 810 may be passed to the processor 1305 andpassed by the processor 1305 to the message interpreter 1320 foradditional processing. For example, the message interpreter 1320 may beconfigured to extract the lower UATI and color code from the UATIassignment message for use in identifying the AT 822 as described above.The message interpreter 1320 may pass the UATI, color code, and otherinformation to the processor 1305 for additional processing. The messageinterpreter 1320 may also interpret information in a request messagereceived from the macro node 805. For example, as described above, themacro node 805 may send a request message to the AT 822 requestingadditional information about the femto node 810. In particular, themacro node 805 may request the color code and lower UATI. The messageinterpreter 1320 may process this request message and provide theprocessor 1305 with information for responding to the request message.The message interpreter 1320 may also be coupled to the memory 1310 tostore or retrieve information for use in message interpreting.

The processor 1305 may also be coupled to a message formatter 1325. Themessage formatter 1325 may generate or format the outbound wirelessmessage to be transmitted by the wireless network interface 1315. Forexample, the message formatter 1325 may be configured to include thelower UATI and color code in the outbound wireless message to the macronode 805. As described above, the message formatter 1325 may beconfigured to include the lower UATI and color code in an outboundwireless message requesting handout from the femto node 810 to the macronode 805. The wireless outbound message may be passed by the messageformatter 1325 to the processor 1305 for transmission by the wirelessnetwork interface 1315 to the macro node 805. The macro node 805 maythen use the information in the outbound wireless message, including thelower UATI and color code, to facilitate identification of the sourceaccess node as described above. The message formatter 1325 may becoupled directly to the memory 1310 in order to store or retrieveinformation for use in message formatting.

The wireless network interface 1315 may comprise an antenna and atransceiver. The transceiver may be configured to modulate/demodulatethe outbound/inbound wireless messages going to or coming from femtonode 810 and the macro node 805. The outbound/inbound wireless messagesmay be transmitted/received via the antenna. The antenna may beconfigured to communicate with the femto node 810 and macro node 805over one or more channels. The outbound/inbound wireless message maycomprise voice and/or data-only information (collectively referred toherein as “data”). The wireless network interface 1315 may demodulatethe data received. The wireless network interface 1315 may modulate datato be sent from the AT 822 via the wireless network interface 1315. Theprocessor 1305 may provide data to be transmitted.

The memory 1310 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1310 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the access terminal 822 need not beseparate structural elements. For example, the processor 1305 and thememory 1310 may be embodied in a single chip. The processor 1305 mayadditionally, or in the alternative, contain memory, such as processorregisters. Similarly, one or more of the functional blocks or portionsof the functionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the AT 822, such asprocessor 1310, message interpreter 1320, and message formatter 1325 maybe embodied as a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anysuitable combination thereof designed to perform the functions describedherein. One or more of the functional blocks and/or one or morecombinations of the functional blocks described with respect to the AT822 may also be implemented as a combination of computing devices, e.g.,a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcommunication, or any other such configuration.

FIG. 14 is a functional block diagram of an exemplary macro node 805shown in FIG. 8. As discussed above with respect to FIG. 8, the macronode 805 may facilitate a hand out from the femto node 810 to the macronode 805 by receiving identifying information from the AT 822 andtransmitting the identifying information to the FGW 852. In anembodiment, the macro node 805 may determine the address of the femtonode 810 and transmit a data session transfer request to the femto node810. The macro node 805 may comprise a wireless network interface 1410configured to receive an inbound wireless message from and transmit anoutbound wireless message to the AT 822. Wireless network interface 1410may be coupled to the processor 1420. The processor 1420 may beconfigured to process the inbound and outbound wireless message comingfrom or going to the AT 822 via the wireless network interface 1410. Theprocessor 1420 may also be configured to control other components of themacro node 805. The processor 1420 may be further coupled to a wirednetwork interface 1430. The wired network interface 1430 may beconfigured to receive an inbound wired message from and to transmit anoutbound wired message to the FGW 852. The wired network interface 1430may receive an inbound wired message and pass the inbound wired messageto the processor 1420 for processing. The processor 1420 may process anoutbound wired message and pass the outbound wired message to the wirednetwork interface 1430 for transmission to the FGW 852.

The processor 1420 may further be coupled, via one or more buses, to amemory 1440. The processor 1420 may read information from or writeinformation to the memory 1440. The memory 1440 may be configured tostore information for use in processing the inbound or outbound, wiredor wireless message. The memory 1440 may also be configured to storeidentifying information such as the address, subnet, and color code ofthe macro node 805. The processor 1420 may also be coupled to a messageinterpreter 1445. The processor may pass the inbound wired and wirelessmessage to the message interpreter 1445 for processing. The messageinterpreter 1445 may be configured to extract information from theinbound wireless message received at the wireless network interface1410. For example, the inbound wireless message received from the AT 822may comprise identifying information such as the lower UATI and thecolor code of a source AN, such as femto node 810. The messageinterpreter 1445 may extract the lower UATI and color code values fromthe inbound wireless message provided by AT 822. The message interpreter1445 may pass this identifying information to the processor 1420 foradditional processing. The message interpreter 1445 may be configured toprocess the inbound wireless message and to provide the processor 1420with information for responding to the inbound wireless message byrequesting additional information. The message interpreter 1445 may alsobe coupled directly to the memory 1440 in order to store or retrieveinformation for use in message interpretation.

The processor 1420 may also be coupled to a message formatter 1450. Themessage formatter 1450 may be configured to generate the outbound wiredor wireless message. The message formatter 1450 may be furtherconfigured to pass the generated outbound wired or wireless message tothe processor 1420. The processor 1420 may pass the outbound wired orwireless message to the wired network interface 1430 or the wirelessnetwork interface 1410 for transmission. The wired network interface1430 may transmit the outbound wired message to the FGW 852. Asdescribed above, the outbound wired message may comprise a sessiontransfer request including the UATI of AT 122. The message formatter1450 may pass the outbound wireless message to the processor 1420. Theprocessor 1420 may pass the outbound wireless message to the wirelessnetwork interface 1410 for transmission to the AT 822. As describedabove, the outbound wireless message may comprise a request foridentifying information of a source AN, such as femto node 810. Themessage formatter 1450 may also be coupled directly to the memory 1440in order to store or retrieve information for use in message formatting.

The wireless network interface 1410 may comprise an antenna and atransceiver. The transceiver may be configured to modulate/demodulatethe outbound/inbound wireless messages going to or coming from the AT822. The inbound/outbound wireless messages may be transmitted/receivedvia the antenna. The antenna may be configured to send and/or receivethe outbound/inbound wireless messages from the macro node 805 over oneor more channels. The outbound/inbound wireless messages may comprisevoice and/or data-only information (collectively referred to herein as“data”). The wireless network interface 1410 may demodulate the datareceived. The wireless network interface 1410 may modulate data to besent from the macro node 805 via the wireless network interface 1410.The processor 1420 may provide data to be transmitted.

The wired network interface 1430 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound wired messagegoing to or coming from the FGW 852. The wired network interface 1430may demodulate the data received according to one or more wiredstandards using methods known in the art. The demodulated data may betransmitted to the processor 1420. The wired network interface 1430 maymodulate data to be sent from the macro node 1410 via the wired networkinterface 1430 according to one or more wired standards using methodsknown in the art. The processor 1420 may provide data to be transmitted.

The memory 1440 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1440 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the macro node 805 need not be separatestructural elements. For example, the processor 1420 and the memory 1440may be embodied in a single chip. The processor 1420 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the macro node 805, suchas processor 1420, message interpreter 1445, and message formatter 1450,may be embodied as a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anysuitable combination thereof designed to perform the functions describedherein. One or more of the functional blocks and/or one or morecombinations of the functional blocks described with respect to themacro node 805 may also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP communication, or any other such configuration.

FIG. 15 is a functional block diagram of an exemplary femto gateway(FGW) 852 shown in FIG. 8. As described above with respect to FIG. 8,the FGW 852 may operate as a router configured to route messages betweenthe macro node 805 and the SGW 854. In addition, the FGW 852 may beconfigured to help identify hand in sources such as the femto node 810by identifying the SGW associated with the femto node 810 based on anidentifier such as an FGW ID, BSC ID, color code, subnet, etc. In anembodiment, the FGW 852 maps a color code and lower UATI to a UATI inorder to determine the address of the femto node 810. The FGW 852 maycomprise a network interface 1510 configured to receive an inboundmessage from and to transmit an outbound message to the macro node 805or the femto node 810 via SGW 854. The network interface 1510 may becoupled to a processor 1520. The processor 1520 may be configured toprocess the inbound message received by and the outbound messagetransmitted by the network interface 1510. The processor 1520 mayfurther be coupled, via one or more buses, to a memory 1525. Theprocessor 1520 may read information from or write information to thememory 1525. The memory 1525 may be configured to store the inbound andoutbound message before, during, or after processing. In particular, thememory 1525 may be configured to store an identifier such as the FGW ID,BSC ID, color code, subnet, etc.

The processor 1520 may be further coupled to a routing unit 1530. Theprocessor 1520 may pass the inbound message to the routing unit 1530 foradditional processing. The routing unit 1530 may analyze the inboundmessage to determine one or more destinations based, at least in part onthe content of the inbound message. For example, the inbound message maycontain the color code and/or BSC_ID of the femto node 810. The routingunit 1530 may analyze the color code and/or BSC_ID and determine thatthe femto node 810 is associated with the SGW 854. The routing unit 1530may be directly coupled to the memory 1525 to facilitate making routingdecisions. For example, the memory 1525 may store a data structure,e.g., a list or table, containing information associating BSC_ID valueswith addresses or other identifiers for SGWs. The routing unit 1530 maybe configured to look up the identifiers for an SGW in the memory 1525using the BSC_ID. The routing unit 1530 may also be configured toprovide information to the processor 1520 such as an address or otheridentifier for the SGW 854 to which the BSC_ID and other informationshould be sent. The processor 1520 may be configured to use thisinformation from the routing unit 1530 to generate the outbound message.The processor 1520 may pass the outbound message to the networkinterface 1510 for transmission to the SGW 854.

The network interface 1510 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound messages. Thenetwork interface 1510 may demodulate the data received according. Thedemodulated data may be transmitted to the processor 1520. The networkinterface 1510 may modulate data to be sent from the FGW 852. Data to besent may be received from the processor 1520.

The memory 1525 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1525 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the FGW 852 need not be separatestructural elements. For example, the processor 1520 and the memory 1525may be embodied in a single chip. The processor 1520 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the FGW 852, such asprocessor 1520 and routing unit 1530 may be embodied as a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, or any suitable combination thereofdesigned to perform the functions described herein. One or more of thefunctional blocks and/or one or more combinations of the functionalblocks described with respect to the FGW 852 may also be implemented asa combination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP communication, or any othersuch configuration.

FIG. 16 is a functional block diagram of an exemplary security gatewayshown in FIG. 8. As described above with respect to FIG. 8, the SGW 854may operate as a transparent tunnel configured to route messages betweenthe FGW 852 and the femto node 810 via Internet 840. The SGW 854 maycomprise a network interface 1610 configured to receive an inboundmessage from and to transmit an outbound message to the FGW 852 or thefemto node 810 via the Internet 840. The network interface 1610 may becoupled to a processor 1620. The processor 1620 may be configured toprocess the inbound and outbound messages. The processor 1620 mayfurther be coupled, via one or more buses, to a memory 1625. Theprocessor 1620 may read information from or write information to thememory 1625. The memory 1625 may be configured to store the inbound andoutbound messages before, during, or after processing. In particular,the memory 1625 may be configured to store the color code and/or BSC_IDdescribed above.

The processor 1620 may be further coupled to a routing unit 1630. Theprocessor 1620 may pass the inbound message to the routing unit 1630 foradditional processing. The routing unit 1630 may analyze the inboundmessage to determine one or more destinations based, at least in part onthe content of the inbound message. For example, the inbound message maycomprise a color code and/or BSC_ID. The routing unit 1630 may analyzethe color code and/or BSC_ID and determine that the femto node isassociated with the identifier. The routing unit 1630 may be directlycoupled to the memory 1625 to facilitate making routing decisions. Forexample, the memory 1625 may store a data structure, e.g., a list ortable, containing information associating color code and/or BSC_IDvalues with addresses or other identifiers for femto nodes. The routingunit 1630 may be configured to look up the identifiers for a femto nodein the memory 1625 using the color code and/or BSC_ID. The routing unit1630 may be configured to provide information to the processor 1620 suchas an address or other identifier for the femto node that is the hand insource. The processor 1620 may be configured to use this informationfrom the routing unit 1630 to generate the outbound message. Theprocessor 1620 may pass the outbound message to the network interface1610 for transmission to the Internet 840 or to the FGW 852.

The network interface 1610 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound messages going toor coming from the SGW 854. The network interface 1610 may demodulatethe data received. The demodulated data may be transmitted to theprocessor 1620. The network interface 1610 may modulate data to be sentfrom the FGW 852. Data to be sent may be received from the processor1620.

The memory 1625 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1625 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the SGW 854 need not be separatestructural elements. For example, the processor 1620 and the memory 1625may be embodied in a single chip. The processor 1620 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the SGW 854, such asprocessor 1620 and routing unit 1630 may be embodied as a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, or any suitable combination thereofdesigned to perform the functions described herein. One or more of thefunctional blocks and/or one or more combinations of the functionalblocks described with respect to the SGW 854 may also be implemented asa combination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP communication, or any othersuch configuration.

B. DNS Address Resolution

In one embodiment, the communication network may incorporate a domainname system (DNS) in order to facilitate source access node addresslookup during a handout procedure. FIG. 17 illustrates exemplaryinteroperations of two or more communication networks using a DNS 1760.In the illustrated embodiment, in which many elements may be generallysimilar to those shown in FIG. 8, macro node 1705 communicates with AT1720 and AT 1722, all of which operate within macro area 1730. Femtonode 1710 communicates with AT 1710, both of which operate within femtoarea 1715. Similarly, femto node 1712 communicates with AT 1721, both ofwhich operate in femto area 1715. FGW 1752, operating in communicationnetwork 1750, may communicate with one or more of the macro node 1705,SGW 1754, and DNS 1760. The Internet 1740 may communicate with femtonodes 1710, 1712, and SGW 1754. In the illustrated embodiment, the DNS1760 is connected to the Internet 1740. In other embodiments, the DNS1760 may be co-located with other functions, such as FGW 1752 or SGW1754, or may be deployed in a different location. In some embodiments,the DNS 1760 may be implemented as a server. In some embodiments, theDNS 1760 may be implemented as a function integrated with anotherelement of the communication network. In some embodiments, more than oneDNS is available. In some embodiments, hierarchical DNSs are available.In some embodiments, there is at least one DNS per macro subnet.

FIG. 18 is a flowchart of an exemplary process for registering anaddress of a source node shown in FIG. 17. As described above withrespect to FIG. 17, the process 1800 may be used to register the addressof a source node allowing later retrieval by a target node. In someembodiments, the source node may be femto node 1710 and the target nodemay be macro node 1705. To facilitate hand in a source node such asfemto node 1710 may assign a first and second identifier to an AT suchas AT 1722, as shown in step 1810. In some embodiments, the firstidentifier may comprise a color code. In other embodiments, the firstidentifier may comprise one or more bits from the upper UATI. In someembodiments, the second identifier may comprise one or more bits fromthe lower UATI.

Continuing to step 1820, the source node generates a domain name basedupon the first and second identifiers. The domain name may be formattedas a character string. In one embodiment, the domain name may be in theform “uati32-<UATI32>.subnet-<subnet>.HRPD.RAN.<operator's domain>”where <UATI32> represents the 32 least significant bits of the UATI,<subnet> represents a character string identifying the subnet of thesource node, and <operator's domain> represents a character stringidentifying the communication network operator's domain. The UATI32 maybe formatted, for example, in a binary or hexadecimal representation.The domain name may include hard or soft-coded strings such as “HRPD”and “RAN” to signify, for instance an HRPD session in a radio areanetwork (RAN). As an example, if the UATI32 is 0xF000F000, the subnet is“subnet A”, and the operator's domain is “example.com”, the domain namemay be “uati32-F000F000.subnet-A.HRPD.RAN.example.com”.

In another embodiment, the domain name may be in the form“uati24-<UATI24>.uati104-<UATI104>.HRPD.RAN.<operator's domain>” where<UATI24> represents the UATI24, <UATI104> represents the UATI104, and<operator's domain> represents a character string identifying thecommunication network operator's domain. For example, if the UATI24 is0xF00F00, the UATI104 is 0x0123456789ABC, and the operator's domain is“example.com”, the domain name may be“uati24-F00F00.uati104-0123456789ABC.HRPD.RAN.example.com”. It will beunderstood that the foregoing embodiments are merely examples, and otherdomain names may be used.

Proceeding to step 1830, the source node obtains its IP address. Invarious embodiments, the source node may obtain its IP address from itswired or wireless network interface, accessing an IP address stored in amemory, or the like. Moving to step 1840, the source node sends a DNSregistration request including the generated domain name and the IPaddress of the source node to a DNS such as DNS 1760. Then, in step1850, the DNS receives the DNS registration request and extracts thedomain name and the IP address of the source node. Finally, in step1860, the DNS associates the IP address of the source node with theprovided domain name in a memory.

FIG. 19 is a functional block diagram of an exemplary DNS 1760 shown inFIG. 17. As discussed above with respect to FIG. 17, the DNS 1760 mayfacilitate a hand out from the femto node 1710 to the macro node 1705 byrecording the address of the femto node 1710 via a registrationprocedure and supplying the address of the femto node 1710 to the macronode 1705 via a DNS query procedure. The DNS 1760 may comprise aprocessor 1920 coupled to a wired network interface 1930. The wirednetwork interface 1930 may be configured to receive an inbound wiredmessage from and to transmit an outbound wired message to an address.The wired network interface 1930 may receive an inbound wired messageand pass the inbound wired message to the processor 1920 for processing.The processor 1920 may process an outbound wired message and pass theoutbound wired message to the wired network interface 1930 fortransmission to an address. For example, during a domain registrationprocedure, the wired network interface 1930 may receive a domainregistration request from the femto node 1710 and pass the domainregistration request to the processor 1920 for processing. During a DNSquery procedure, the wired network interface 1930 may receive a DNSquery from the macro node 1705 and pass the DNS query to the processor1920 for processing. The processor 1920 may pass formatted responses tothe wired network interface 1930 for transmission to, for example, thefemto node 1710 and/or the macro node 1705.

The processor 1920 may further be coupled, via one or more buses, to amemory 1940. The processor 1920 may read information from or writeinformation to the memory 1940. The memory 1940 may be configured tostore information for use in processing the inbound or outbound wiredmessage. The memory 1940 may also be configured to store domaininformation such as a domain name and an associated IP address. Theprocessor 1920 may also be coupled to a message interpreter 1945. Theprocessor may pass the inbound wired message to the message interpreter1945 for processing. The message interpreter 1945 may be configured toextract information from the inbound wired message received at the wirednetwork interface 1930. For example, the inbound DNS registrationrequest received from femto node 1710 may comprise domain informationsuch as a domain name and an IP address. The message interpreter 1945may extract the domain name and the IP address from the inbound wiredmessage provided by femto node 1710. The message interpreter 1945 maypass this identifying information to the processor 1920 for additionalprocessing. The message interpreter 1945 may also be coupled directly tothe memory 1940 in order to store or retrieve information for use inmessage interpretation.

The processor 1920 may also be coupled to a message formatter 1950. Themessage formatter 1950 may be configured to generate the outbound wiredmessage. The message formatter 1950 may be further configured to passthe generated outbound wired message to the processor 1920. Theprocessor 1920 may pass the outbound wired message to the wired networkinterface 1930 for transmission. The wired network interface 1930 maytransmit the outbound wired message to, for example, the femto node 1710and/or the macro node 1705. The outbound wired message may comprise aDNS registration response, such as an acknowledgement or a negativeacknowledgement. The outbound wired message may also comprise a DNSquery response, including an IP address of the queried domain name. Themessage formatter 1950 may also be coupled directly to the memory 1940in order to store or retrieve information for use in message formatting.

The wired network interface 1930 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound wired messagegoing to or coming from a network address. The wired network interface1930 may demodulate the data received according to one or more wiredstandards using methods known in the art. The demodulated data may betransmitted to the processor 1920. The wired network interface 1930 maymodulate data to be sent from the macro node 1910 via the wired networkinterface 1930 according to one or more wired standards using methodsknown in the art. The processor 1920 may provide data to be transmitted.

The memory 1940 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 1940 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the DNS 1760 need not be separatestructural elements. For example, the processor 1920 and the memory 1940may be embodied in a single chip. The processor 1920 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the DNS 1760, such asprocessor 1920, message interpreter 1945, and message formatter 1950,may be embodied as a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anysuitable combination thereof designed to perform the functions describedherein. One or more of the functional blocks and/or one or morecombinations of the functional blocks described with respect to the DNS1760 may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcommunication, or any other such configuration.

FIG. 20 is a flowchart of an exemplary process for identifying anaddress of a source node shown in FIG. 17. As described with respect toFIG. 17, the process 2000 may be used to help identify the address of asource node during a hand in process to a target node. To facilitatehand in, an AT such as AT 1722 transmits a first and second identifierto a target access node such as macro node 1705, as shown in step 2010.The first identifier may comprise the color code that the AT 1722previously received from the femto node1 810. Alternatively, the firstidentifier may comprise one or more bits of the upper UATI that the AT1722 previously received from the femto node 1710. The second identifiermay comprise the lower UATI that the AT 1722 previously received fromthe femto node 1710. In an embodiment, the femto node 1710 may havegenerated a UATI and assigned the UATI to the AT 1722. The femto node1710 may have generated a domain name based on the first and secondidentifiers and registered its IP address and domain name with the DNS1760. Proceeding to step 2020, the target access node receives the firstand second identifier.

Continuing to step 2030, the source node generates a domain name basedupon the first and second identifiers. The domain name may be formattedas a character string. In one embodiment, the domain name may be in theform “uati32-<UATI32>.subnet-<subnet>.HRPD.RAN.<operator's domain>”where <UATI32> represents the 32 least significant bits of the UATI,<subnet> represents a character string identifying the subnet of thesource node, and <operator's domain> represents a character stringidentifying the communication network operator's domain. The UATI32 maybe formatted, for example, in a binary or hexadecimal representation.The domain name may include hard or soft-coded strings such as “HRPD”and “RAN” to signify, for instance an HRPD session in a radio areanetwork (RAN). As an example, if the UATI32 is 0xF000F000, the subnet is“subnet A”, and the operator's domain is “example.com”, the domain namemay be “uati32-F000F000.subnet-A.HRPD.RAN.example.com”.

In another embodiment, the domain name may be in the form“uati24-<UATI24>.uati104-<UATI104>.HRPD.RAN.<operator's domain>” where<UATI24> represents the UATI24, <UATI104> represents the UATI104, and<operator's domain> represents a character string identifying thecommunication network operator's domain. For example, if the UATI24 is0xF00F00, the UATI104 is 0x0123456789ABC, and the operator's domain is“example.com”, the domain name may be“uati24-F00F00.uati104-0123456789ABC.HRPD.RAN.example.com”. It will beunderstood that the foregoing embodiments are merely examples, and otherdomain names may be used.

Proceeding to step 2040, the target node sends a domain name query to aDNS such as DNS 1760. In step 2050, the DNS receives the DNS query andextracts the domain name from the query. Then, in step 2060, the DNSmaps the domain name to the IP address of the source node. In anembodiment, the DNS performs a lookup based upon the domain name andretrieves the associated IP address from memory. Moving to step 2070,the DNS formats a query response including the IP address of the sourcenode and sends the response to the target access node.

Finally, in step 2080, the target access node receives the queryresponse from the DNS. In an embodiment, the target access node extractsthe IP address of the source node from the query response. In anembodiment, the target access node may send a session transfer requestto the IP address of the source node, and proceeds as shown in FIG. 6.

C. Proxy

In one embodiment, the communication network may incorporate a proxy inorder to facilitate communication between a target access node and asource access node during a handout procedure. FIG. 21 illustratesexemplary interoperations of two or more communication networksimplementing a proxy 2170. In the illustrated embodiment, in which manyelements may be generally similar to those shown in FIG. 8, macro node2105 communicates with AT 2120 and AT 2122, all of which operate withinmacro area 2130. Femto node 2110 communicates with AT 2110, both ofwhich operate within femto area 2115. Similarly, femto node 2112communicates with AT 2121, both of which operate in femto area 171. FGW2152, operating in communication network 2150, may communicate with oneor more of the macro node 2105, SGW 2154, and a proxy 2170. The Internet2140 may communicate with femto nodes 2110, 2112, and SGW 2154.

In the illustrated embodiment, the proxy 2170 is co-located with theFGW, and communicates with the macro node 2105 and the SGW 2154. Inother embodiments, the proxy 2170 may be co-located with otherfunctions, may operate as a stand-alone element, or may be deployed in adifferent location. In some embodiments, the proxy 2170 may beimplemented as a server. In some embodiments, the proxy 2170 may beimplemented as a function integrated with another element of thecommunication network. In some embodiments, more than one proxy isavailable. In some embodiments, the proxy 2170 is a proxy for A13messages.

In some embodiments, the proxy 2170 may act as a stateful proxy. Inacting as a stateful proxy, the proxy 2170 may maintain a record thestate of communications between two nodes. The proxy 2170 may allow atarget node to send a message to a source node without determining theaddress of the source node. For example, the proxy 2170 may statefullyfacilitate communication between macro node 2105 and femto node 2110without the macro node 2105 obtaining the address of femto node 2110. Inan embodiment, macro node 2105 may statefully communicate with the proxy2170 as if the proxy were another macro node. The proxy may communicatewith femto node 2110 on the behalf of macro node 2105. As such, incommunicating with femto node 2110 through the proxy 2170, the macronode 2105 may follow the same steps and/or procedures as it would ifthere were no femto nodes and/or proxies in the communication network.In an embodiment, the proxy 2170 may alter messages from the macro node2105 such that they appear to originate from the proxy 2170.Furthermore, the proxy 2170 may alter messages from the macro node 2105such that responses from the femto node 2110 are intercepted by theproxy 2170. The proxy 2170 may statefully communicate with the macronode 2105 on behalf of the femto node 2110. As such, in communicatingwith macro node 2105 through the proxy 2170, the femto node 2105 mayfollow the same steps and/or procedures as it would if there were noproxies in the communication network.

In some embodiments, the proxy 2170 may act as a stateless proxy. Inacting as a stateless proxy, the proxy 2170 may facilitate communicationbetween two nodes without maintaining a record of the state of thatcommunication. The proxy 2170 may allow a target node to send a messageto a source node without initially determining the address of the sourcenode. For example, the proxy 2170 may statelessly facilitatecommunication between macro node 2105 and femto node 2110 without themacro node 2105 initially obtaining the address of femto node 2110. Inan embodiment, macro node 2105 may communicate with the proxy 2170 as ifthe proxy were another macro node. The proxy may communicate with femtonode 2110 on the behalf of macro node 2105. As such, in initiallycommunicating with femto node 2110 through the proxy 2170, the macronode 2105 may follow the same steps and/or procedures as it would ifthere were no femto nodes and/or proxies in the communication network.In an embodiment, the proxy 2170 may forward messages from the macronode 2105 such that they appear to originate from the macro node 2105.Thus, the femto node 2110 may obtain the address of the macro node 2105and may send responses directly to the macro node 2105, bypassing theproxy 2170. Responses from the femto node 2110 to the macro node 2105may contain information identifying the address of the femto node 2110.The macro node 2105 may receive responses from the femto node 2110 anddetermine the address of the femto node 2110. The macro node 2105 maysend subsequent messages directly to the femto node 2110, bypassing theproxy 2170.

FIG. 22A illustrates an exemplary identifier assignment scheme used by afemto node in a communication system including a proxy. In anembodiment, femto assignment scheme 2200 may be used by femto node 2110when assigning a UATI 2205 to an AT such as AT 2122 (see FIG. 21).Assignment scheme 2200 may be generally similar to assignment scheme900, shown in FIG. 9A. For example, UATI 2205 may comprise lower UATI2210, including ATID 2215 and BSC_ID_LSB 2220. UATI 2205 may alsocomprise upper UATI 2225, including BSC_ID_MSB 2230. Together,BSC_ID_MSB 2230 and BSC_ID_LSB 2220 may compose one or more bits ofBSC_ID 2240. In some embodiments, BSC_ID 2235 may represent the IPaddress of the femto node 2110. In some embodiments, the BSC_ID 2235 maymap to the address of the femto cell.

In an embodiment, however, lower UATI 2210 may also include one or moreLSBs of a proxy identifier (Proxy_ID_LSB) 2245. Proxy_ID_LSB 2245 mayoccupy one or more of the MSBs of the lower UATI. In an embodiment,BSC_ID_MSB 2230 may also be interpreted as the MSBs of the proxyidentifier (Proxy_ID_MSB) 2230. In an embodiment, Proxy_ID_MSB, togetherwith Proxy_ID_LSB, may compose one or more bits of the proxy identifier(Proxy_ID) 2235. As will be discussed below with reference to FIG. 22B,Proxy_ID 2235 may be the same size as the BSC_ID associated with themacro node 2105. In some embodiments, Proxy_ID 2240 may represent the IPaddress of the femto node 2110. In some embodiments, the BSC_ID 2240 maymap to the address of the femto cell.

FIG. 22B illustrates an exemplary identifier assignment scheme used by amacro node in a communication system including a proxy. In anembodiment, macro assignment scheme 2250 may be used by macro node 2105when assigning a UATI 2255 to an AT such as AT 2122 (see FIG. 21). Insome embodiments, macro assignment scheme 2250 may comprise theassignment scheme used for UATI 510 shown in FIG. 5. For example, UATI2255 may comprise lower UATI 2260, including ATID 2265 and BSC_ID_LSB2270. UATI 2255 may also comprise upper UATI 2275, including BSC_ID_MSB2280. Together, BSC_ID_MSB 2280 and BSC_ID_LSB 2270 may compose one ormore bits of BSC_ID 2285. In some embodiments, BSC_ID 2285 may representthe IP address of the femto node 2110. In some embodiments, the BSC_ID2235 may map to the address of the femto cell.

In some embodiments, the BSC_ID 2285 may be the same size as theProxy_ID 2235. This may allow a target cell such as macro node 2105 toprocess a UATI using the femto UATI assignment scheme 2200 in the samemanner as any other macro node. In other words, the proxy may beaddressed according to existing methodologies. In embodiments where theProxy_ID is format-compatible with the BSC_ID used in the macro UATIassignment scheme 2250, a proxy may function as a drop-in networkelement without modification to the macro nodes.

FIG. 23 is a flowchart of an exemplary process for relaying a messagefrom a target access node to a source access node by a proxy 2170 shownin FIG. 21. As described above with respect to FIG. 21, the process 2300may be used to facilitate communication between a target access node anda source access node.

As shown in step 2310, an access terminal transmits a first and secondidentifier to a target access node. In an embodiment, the accessterminal may be AT 2122 and the target access node may be macro node2105. The first identifier may comprise the color code that the AT 2122previously received from the femto node 2110. Alternatively, the firstidentifier may comprise one or more bits of the upper UATI that the AT2122 previously received from the femto node 2110. The second identifiermay comprise the lower UATI that the AT 2122 previously received fromthe femto node 2110. In an embodiment, the femto node 2110 may havegenerated a UATI and assigned the UATI to the AT 2122. The AT 2122 mayhave resolved the color code from one or more bits of the UATI. Inanother embodiment, the femto node 2110 may have transmitted the boththe color code and one or more bits of the UATI to the AT 2122. The AT2122 may have stored the color code and the UATI in a memory. In anembodiment, the UATI generated by the femto node 2110 may contain theBSC_ID of the proxy 2170, instead of the BSC_ID of the femto node 2110.In another embodiment, the color code used by the femto node 2110 may beassociated with the address of the proxy 2170 in the lookup tables ofmacro node 2105.

Continuing to step 2320, the target access node receives the first andsecond identifier from the AT. In some embodiments, the macro node 2105may receive the color code and the lower UATI from the AT 2122. Themacro node 2105 may store the color code and lower UATI in a memory. Inone embodiment, the macro node 2105 may forward the color code and lowerUATI to the FGW 2152 for processing.

Next, in step 2330, proxy 2170 maps the first and second identifiers toan address. In an embodiment, proxy 2170 may map the identifiers in amanner generally similar to that as shown in FIG. 5 and described withrespect to FIG. 6. However, in some embodiments the Proxy_ID may occupythe bits normally used for the BSC_ID. For example, macro node 2105 maymap the color code to an upper UATI and combine one or more bits fromthe upper UATI with one or more bits from the lower UATI to extract theProxy_ID of the proxy 2170. In another embodiment, the macro node 2105may perform a memory lookup on the color code and retrieve an associatedIP address.

In some embodiments, the macro node 2105 may follow the same stepsand/or procedures as it would if there were no femto nodes and/orproxies in the communication network. In some embodiments, because thefemto node 2110 previously supplied the AT 2122 with identifiersincluding the Proxy_ID in place of the BSC_ID, the target AN mayretrieve the IP address of the proxy 2170 instead of the address of thefemto 2110.

Proceeding to step 2340, the target node sends a session informationmessage including the first and second identifiers to the IP address ofthe proxy 2170. In some embodiments, the session information message maycomprise an A13 message. In some embodiments, the session informationmessage may comprise a data session transfer request. Then, in step2350, the proxy 2170 receives the session information message from thetarget node. The proxy 2170 may store the session information message ina memory.

In steps 2360-2280, the proxy 2170 determines the address of the sourcenode. In an embodiment, the proxy 2170 determines the address of thesource node in a manner generally similar to that shown in FIG. 10. Forexample, in step 2360, the proxy 2170 may determine an access node typeof the source access node based upon the first identifier. Possible nodetypes may include macro nodes and femto nodes. The proxy 2170 mayperform a lookup on the first identifier in order to determine whetherthe source node is a macro or femto node. In embodiments where the firstidentifier comprises the color code of the source node, one or morecolor codes may be reserved to identify the source node as a femto node.In embodiments where the first identifier comprises one or more bits ofthe upper UATI, the proxy 2170 may first map the first identifier to asubnet and/or BSC_ID_MSB and then compare the result with a list ofknown femto nodes.

Thereafter, in step 2370, the proxy 2170 partitions the secondidentifier into a source access node code and an access terminal code.In an embodiment, the second identifier may be the lower UATI as shownin FIG. 22A and FIG. 22B. Thus, the source access node code may comprisethe BSC_ID_LSB and the access terminal code may comprise the ATID. In anembodiment, the proxy 2170 may partition the second identifier as shownin 22A and 22B. For example, if the proxy 2170 determines the accessnode to be a femto node, the proxy 2170 may extract the BSC_ID_LSB andATID in accordance with femto UATI assignment scheme 2200, shown in FIG.22A. Alternatively, if the proxy 2170 determines the access node to be amacro node, the proxy 2170 may extract the BSC_ID_LSB and ATID inaccordance with macro UATI assignment scheme 2250, shown in FIG. 22B.Thus, when the source access node is a femto node, the extractedBSC_ID_LSB may have more bits than when the source access node is amacro node. Similarly, when the source access node is a femto node, theextracted ATID may have fewer bits than when the source access node is amacro node. The proxy 2170 may store the BSC_ID_LSB and/or ATID in amemory.

Subsequently, in step 2380, the proxy 2170 obtains the address of thesource access node. When the source access node is a femto node, theproxy 2170 may map the color code to an upper UATI and extract theBSC_ID_MSB as shown in FIG. 5. The proxy 2170 may concatenate theBSC_ID_MSB with the BSC_ID_LSB to form the BSC_ID. In some embodiments,the BSC_ID of the femto access node may be the IP address of the sourceaccess node. When the source access node is a macro node, the proxy 2170may simply perform a lookup on the color code to determine the IPaddress of the source access node. In some embodiments, the proxy 2170may map the color code to an upper UATI and extract the BSC_ID_MSB asshown in FIG. 5. The proxy 2170 may concatenate the BSC_ID_MSB with theBSC_ID_LSB to form the BSC_ID. In some embodiments, the BSC_ID of themacro access node may be the IP address of the source access node.

Finally, in step 2390, the proxy 2170 forwards the session informationmessage to the source access node at the address obtained in step 2380.In some embodiments, the proxy 2170 may statelessly forward the message.The proxy 2170 may modify the message and/or relevant transmissionprotocol such that it appears to the source node that the forwardedmessage has been sent directly from the target node. For example, whenforwarding a message from macro node 2105 to femto node 2110, the proxy2170 may spoof the source address of a transmission packet by replacingthe address of the proxy 2170 with the address of the target node 2105.In some embodiments, proxy 2170 may spoof the IP address of the senderof the message by modifying a source IP address field of an IP packetcomprising one or more bits of the message.

FIG. 24 is a flowchart of an exemplary process for statefully relaying amessage by a proxy 2170 shown in FIG. 21. As described above withrespect to FIG. 21, the process 2400 may be used to facilitatecommunication between a target access node and a source access node bythe proxy 2170.

As shown in exemplary step 2410, the proxy receives a message from asource communication node. In an embodiment, the proxy may be proxy 2170and the source communication node may be macro node 2105, as shown inFIG. 21. In an alternative embodiment, the source communication node maybe femto node 2110.

Continuing to step 2420, the proxy loads available session stateinformation. In an embodiment, the proxy may determine the IP address ofthe message sender and retrieve related state information from a memory.State information may include the address of a target communication nodewith which the source communication node intends to communicate, ahistory of communications between the two communication nodes, andinformation that may help interpret the content of the message. Forexample, macro node 2105 may send a new data session transfer request tothe proxy 2180. In this case, proxy 2170 may not retrieve any stateinformation. In another example, femto node 2110 may send a response toa data session transfer request to the proxy 2180. In this case, proxy2170 may retrieve a record of a data session transfer request previouslyforwarded from macro node 2105.

Next, in step 2430, the proxy 2170 determines the message destination.In some embodiments, the proxy 2170 may extract a destination addressfrom the message data. For example, as described with respect to FIG.23, proxy 2170 may receive a data session transfer request from macronode 2105. The proxy 2170 may map first and second identifiers embeddedwithin the data session transfer request to the address of the femtonode 2110. In some embodiments, the proxy 2170 may determine thedestination address from state information loaded from memory in step2420. For example, proxy 2170 may receive a response to a data sessiontransfer request from femto node 2110. The proxy 2170 may extract theaddress of the femto node 2110 from a source IP address field of an IPpacket and look up the address in stored transmission logs. The proxy2170 may determine that it previously relayed the data session transferrequest from macro node 2105 and may therefore determine that the propermessage destination is the macro node 2105. In other embodiments, theproxy 2170 may determine the destination address from an externalsource, such by querying a DNS as described above with respect to FIG.17.

Then, in step 2440, the proxy 2170 modifies the message such thatresponses will be intercepted by the proxy. In an embodiment, proxy 2170replaces all occurrences of the address of the sender of the messagewith the address of the proxy 2170. For example, the proxy 2170 mayreceive a data session transfer request from macro node 2105. The proxy2170 may replace all instances of the address of macro node 2105 withthe address of proxy 2170. In another example, the proxy 2170 mayreceive a data session transfer response from femto node 2110. The proxy2170 may replace all instances of the address of femto node 2110 withthe address of proxy 2170.

Moving to step 2450, the proxy 2170 sends the modified message to themessage destination, as determined in step 2430. For example, the proxy2170 may transmit the modified message to the IP address of the femtonode 2110. In another example, the proxy 2170 may transmit the modifiedmessage to the IP address of the macro node 2105.

Finally, in step 2450, the proxy 2170 records state informationpertaining to the forwarded message. In an embodiment, the proxy 2170may record information such as the message type, source address,destination address, actions taken, and the like. For example, afterforwarding a data session transfer request from macro node 2105 to femtonode 2110, proxy 2170 may record one or more of the address of the macronode 2105, the address of the femto node 2110, and the data sessiontransfer request message type. In another example, after forwarding aresponse to a data session transfer request from femto node 2110 tomacro node 2105, proxy 2170 may record one or more of the address of themacro node 2105, the address of the femto node 2110, and the datasession transfer response message type.

FIG. 25 is a flowchart of an exemplary process for statefully relaying amessage from a target access node to a source access node by proxy 2170shown in FIG. 21. As described above with respect to FIG. 21, theprocess 2500 may be used to facilitate communication between a targetaccess node and a source access node by the proxy 2170.

As shown in exemplary step 2510, an access terminal transmits a firstand second identifier to a target access node. In an embodiment, theaccess terminal may be AT 2122 and the target access node may be macronode 2105. The first identifier may comprise the color code that the AT2122 previously received from the femto node 2110. Alternatively, thefirst identifier may comprise one or more bits of the upper UATI thatthe AT 2122 previously received from the femto node 2110. The secondidentifier may comprise the lower UATI that the AT 2122 previouslyreceived from the femto node 2110. In an embodiment, the femto node 2110may have generated a UATI and assigned the UATI to the AT 2122. The AT2122 may have resolved the color code from one or more bits of the UATI.In another embodiment, the femto node 2110 may have transmitted the boththe color code and one or more bits of the UATI to the AT 2122. The AT2122 may have stored the color code and the UATI in a memory. In anembodiment, the UATI generated by the femto node 2110 may contain theBSC_ID of the proxy 2170, instead of the BSC_ID of the femto node 2110.In another embodiment, the color code used by the femto node 2110 may beassociated with the address of the proxy 2170 in the lookup tables ofmacro node 2105.

Continuing to step 2520, the target access node receives the first andsecond identifier from the AT. In some embodiments, the macro node 2105may receive the color code and the lower UATI from the AT 2122. Themacro node 2105 may store the color code and lower UATI in a memory. Inone embodiment, the macro node 2105 may forward the color code and lowerUATI to the FGW 2152 for processing.

Then, in step 2530, proxy 2170 maps the first and second identifiers toan address, as shown in FIG. 5 and described with respect to FIG. 6. Forexample, macro node 2105 may map the color code to an upper UATI andcombine one or more bits from the upper UATI with one or more bits fromthe lower UATI to extract the BSC_ID of the proxy 2170. In anotherembodiment, the macro node 2105 may perform a memory lookup on the colorcode and retrieve an associated IP address. In some embodiments, themacro node 2105 may follow the same steps and/or procedures as it wouldif there were no femto nodes and/or proxies in the communicationnetwork. In some embodiments, because the femto node 2110 previouslysupplied the AT 2122 with identifiers associated with the proxy 2170,the target AN will retrieve the IP address of the proxy 2170 instead ofthe address of the femto 2110.

Moving to step 2540, the target node sends a session information messageincluding the first and second identifiers to the IP address of theproxy 2170. In some embodiments, the session information message maycomprise an A13 message. In some embodiments, the session informationmessage may comprise a data session transfer request. Next, in step2550, the proxy 2170 receives the session information message from thetarget node. The proxy 2170 may store the session information message ina memory.

In steps 2560-2480, the proxy 2170 determines the address of the sourcenode. In an embodiment, the proxy 2170 determines the address of thesource node in a manner generally similar to that shown in FIG. 10. Forexample, in step 2560, the proxy 2170 may determine an access node typeof the source access node based upon the first identifier. Possible nodetypes may include macro nodes and femto nodes. The proxy 2170 mayperform a lookup on the first identifier in order to determine whetherthe source node is a macro or femto node. In embodiments where the firstidentifier comprises the color code of the source node, one or morecolor codes may be reserved to identify the source node as a femto node.In embodiments where the first identifier comprises one or more bits ofthe upper UATI, the proxy 2170 may first map the first identifier to asubnet and/or BSC_ID_MSB and then compare the result with a list ofknown femto nodes.

Proceeding to step 2585, the proxy 2170 partitions the second identifierinto a source access node code and an access terminal code. In anembodiment, the second identifier may be the lower UATI as shown in FIG.22A and FIG. 22B. Thus, the source access node code may comprise theBSC_ID_LSB and the access terminal code may comprise the ATID. In anembodiment, the proxy 2170 may partition the second identifier as shownin 22A and 22B. For example, if the proxy 2170 determines the accessnode to be a femto node, the proxy 2170 may extract the BSC_ID_LSB andATID in accordance with femto UATI assignment scheme 2200, shown in FIG.22A. Alternatively, if the proxy 2170 determines the access node to be amacro node, the proxy 2170 may extract the BSC_ID_LSB and ATID inaccordance with macro UATI assignment scheme 2250, shown in FIG. 22B.Thus, when the source access node is a femto node, the extractedBSC_ID_LSB may have more bits than when the source access node is amacro node. Similarly, when the source access node is a femto node, theextracted ATID may have fewer bits than when the source access node is amacro node. The proxy 2170 may store the BSC_ID_LSB and/or ATID in amemory.

Thereafter, in step 2580, the proxy 2170 obtains the address of thesource access node. When the source access node is a femto node, theproxy 2170 may map the color code to an upper UATI and extract theBSC_ID_MSB as shown in FIG. 5. The proxy 2170 may concatenate theBSC_ID_MSB with the BSC_ID_LSB to form the BSC_ID. In some embodiments,the BSC_ID of the femto access node may be the IP address of the sourceaccess node. When the source access node is a macro node, the proxy 2170may simply perform a lookup on the color code to determine the IPaddress of the source access node. In some embodiments, the proxy 2170may map the color code to an upper UATI and extract the BSC_ID_MSB asshown in FIG. 5. The proxy 2170 may concatenate the BSC_ID_MSB with theBSC_ID_LSB to form the BSC_ID. In some embodiments, the BSC_ID of themacro access node may be the IP address of the source access node.

Subsequently, in step 2585, the proxy 2170 modifies the message suchthat responses will be intercepted by the proxy. In an embodiment, proxy2170 replaces all occurrences of the address of the sender of themessage with the address of the proxy 2170. For example, the proxy 2170may receive a data session transfer request from macro node 2105. Theproxy 2170 may replace all instances of the address of macro node 2105with the address of proxy 2170.

Then, in step 2590, the proxy 2170 sends the modified message to themessage destination, as determined in step 2530. For example, the proxy2170 may transmit the modified message to the IP address of the femtonode 2110.

Finally, in step 2595, the proxy 2170 records state informationpertaining to the forwarded message. In an embodiment, the proxy 2170may record information such as the message type, source address,destination address, actions taken, and the like. For example, afterforwarding a data session transfer request from macro node 2105 to femtonode 2110, proxy 2170 may record one or more of the address of the macronode 2105, the address of the femto node 2110, and the data sessiontransfer request message type.

FIG. 26 is a functional block diagram of an exemplary proxy 2170 shownin FIG. 21. As discussed above with respect to FIG. 21, the proxy 2170may facilitate a hand out from the femto node 2110 to the macro node2105 by performing address translation. The proxy 2170 may comprise aprocessor 2620 coupled to a wired network interface 2630. The wirednetwork interface 2630 may be configured to receive an inbound wiredmessage from and to transmit an outbound wired message to an address.The wired network interface 2630 may receive an inbound wired messageand pass the inbound wired message to the processor 2620 for processing.The processor 2620 may process an outbound wired message and pass theoutbound wired message to the wired network interface 2630 fortransmission to an address. For example, during a handout procedure, thewired network interface 2630 may receive a data session transfer requestfrom the macro node 2105 and pass the data session transfer request tothe processor 2620 for processing. In another example, the wired networkinterface 2630 may receive a data session transfer response from thefemto node 2110 and pass the data session transfer response to theprocessor 2620 for processing. The processor 2620 may pass formattedresponses to the wired network interface 2630 for transmission to asource node and/or a target node. More specifically, in an embodiment,the processor 2620 may pass a modified or unmodified data sessiontransfer request to the wired network interface 2630 for transmission tofemto node 2110. In another embodiment, the processor 2620 may pass amodified or unmodified data session transfer response to the wirednetwork interface 2630 for transmission to macro node 2105.

The processor 2620 may further be coupled, via one or more buses, to amemory 2640. The processor 2620 may read information from or writeinformation to the memory 2640. The memory 2640 may be configured tostore information for use in processing the inbound or outbound wiredmessage. The memory 2640 may also be configured to store stateinformation such as the message type, source address, destinationaddress, actions taken, and the like. The processor 2620 may also becoupled to a message interpreter 2645. The processor may pass theinbound wired message to the message interpreter 2645 for processing.The message interpreter 2645 may be configured to extract informationfrom the inbound wired message received at the wired network interface2630. For example, the inbound data session transfer request receivedfrom macro node 2105 may comprise first and second identifiers, a sourceIP address, a destination IP address, and/or a message type. The messageinterpreter 2645 may extract the information from the inbound wiredmessage provided by femto node 2110 and pass it to the processor 2620for additional processing. The message interpreter 2645 may also becoupled directly to the memory 2640 in order to store or retrieveinformation for use in message interpretation.

The processor 2620 may also be coupled to a message formatter 2650. Themessage formatter 2650 may be configured to generate the outbound wiredmessage. In some embodiments, the outbound wired message may comprise amodified message, as described above with respect to FIG. 21. Themessage formatter 2650 may be further configured to pass the generatedoutbound wired message to the processor 2620. The processor 2620 maypass the outbound wired message to the wired network interface 2630 fortransmission. The wired network interface 2630 may transmit the outboundwired message to, for example, the femto node 2110 and/or the macro node2105. For example, the outbound wired message may comprise a forwardeddata session request or a forwarded data session response. In anotherexample, the outbound wired message may comprise a modified data sessionrequest or a modified data session response. The message formatter 2650may also be coupled directly to the memory 2640 in order to store orretrieve information for use in message formatting.

The wired network interface 2630 may comprise a modem. The modem may beconfigured to modulate/demodulate the outbound/inbound wired messagegoing to or coming from a network address. The wired network interface2630 may demodulate the data received according to one or more wiredstandards using methods known in the art. The demodulated data may betransmitted to the processor 2620. The wired network interface 2630 maymodulate data to be sent from the macro node 2610 via the wired networkinterface 2630 according to one or more wired standards using methodsknown in the art. The processor 2620 may provide data to be transmitted.

The memory 2640 may comprise a processor cache, including a multi-levelhierarchical cache in which different levels have different capacitiesand access speeds. The memory 2640 may also comprise random accessmemory (RAM), other volatile storage devices, or non-volatile storagedevices. The storage may include hard drives, optical discs, such ascompact discs (CDs) or digital video discs (DVDs), flash memory, floppydiscs, magnetic tape, and Zip drives.

Although described separately, it is to be appreciated that functionalblocks described with respect to the proxy 2170 need not be separatestructural elements. For example, the processor 2620 and the memory 2640may be embodied in a single chip. The processor 2620 may additionally,or in the alternative, contain memory, such as processor registers.Similarly, one or more of the functional blocks or portions of thefunctionality of various blocks may be embodied in a single chip.Alternatively, the functionality of a particular block may beimplemented on two or more chips.

One or more of the functional blocks and/or one or more combinations ofthe functional blocks described with respect to the proxy 2170, such asprocessor 2620, message interpreter 2645, and message formatter 2650,may be embodied as a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anysuitable combination thereof designed to perform the functions describedherein. One or more of the functional blocks and/or one or morecombinations of the functional blocks described with respect to theproxy 2170 may also be implemented as a combination of computingdevices, e.g., a combination of a DSP and a microprocessor, a pluralityof microprocessors, one or more microprocessors in conjunction with aDSP communication, or any other such configuration.

The functionality described herein (e.g., with regard to one or more ofthe accompanying figures) may correspond in some aspects to similarlydesignated “means for” functionality in the included claims. Referringto FIG. 27-31, apparatuses 2700, 2800, 2900, 3000, and 3100 arerepresented as a series of interrelated functional modules.

FIG. 27 is a functional block diagram of yet another exemplary macronode, such as macro node 805 in FIG. 8. As shown, the 2700 may comprisea processing module 2705, a storing module 2710, a formatting module2715, an obtaining module 2720, a partitioning module 2725, a receivingmodule 2740, a transmitting module 2741, a communications module 2745,and a transferring module 2750. The processing module 2705 maycorrespond at least in some aspects to, for example, a processor asdiscussed herein. The storing module 2710 may correspond at least insome aspects to, for example, a memory as discussed herein. Theformatting module 2715 may correspond at least in some aspects to, forexample, a message formatter as discussed herein. The obtaining module2720 may correspond at least in some aspects to, for example, a messageinterpreter as discussed herein. In an aspect, the obtaining module 2720may comprise one or more of a mapping module (not shown) and a combiningmodule (not shown). The mapping and combining modules may correspond atleast in some aspects to, for example, a processor as discussed herein.The partitioning module 2725 may correspond at least in some aspects to,for example, a message interpreter as discussed herein. In an aspect,the partitioning module 2725 may comprise an allocating module (notshown). The allocating module may correspond at least in some aspectsto, for example, a processor as discussed herein. The receiving module2740 may correspond at least in some aspects to, for example, a wired orwireless network interface as discussed herein. The transmitting module2741 may correspond at least in some aspects to, for example, a wired orwireless network interface as discussed herein. The communicationsmodule 2745 may correspond at least in some aspects to, for example, aprocessor as discussed herein. The transferring module 2750 maycorrespond at least in some aspects to, for example, a wired or wirelessnetwork interface as discussed herein.

FIG. 28 is a functional block diagram of yet another exemplary macronode, such as macro node 1805 in FIG. 17. As shown, the macro node 2800may comprise a processing module 2805, a storing module 2810, aformatting module 2815, a mapping module 2820, a generating module 2825,a receiving module 2840, a transmitting module 2841, a communicationsmodule 2845, and a transferring module 2850. The processing module 2805may correspond at least in some aspects to, for example, a processor asdiscussed herein. The storing module 2810 may correspond at least insome aspects to, for example, a memory as discussed herein. Theformatting module 2815 may correspond at least in some aspects to, forexample, a message formatter as discussed herein. The mapping module2820 may correspond at least in some aspects to, for example, aprocessor as discussed herein. The generating module 2825 may correspondat least in some aspects to, for example, a processor as discussedherein. In an aspect, the generating module 2825 may comprise one ormore of an obtaining module (not shown) and a creating module (notshown). The obtaining module may correspond at least in some aspects to,for example, a message interpreter as discussed herein. The creatingmodule may correspond at least in some aspects to, for example, amessage formatter as discussed herein. The receiving module 2840 maycorrespond at least in some aspects to, for example, a wired or wirelessnetwork interface as discussed herein. The transmitting module 2841 maycorrespond at least in some aspects to, for example, a wired or wirelessnetwork interface as discussed herein. The communications module 2845may correspond at least in some aspects to, for example, a processor asdiscussed herein. The transferring module 2850 may correspond at leastin some aspects to, for example, a wired or wireless network interfaceas discussed herein.

FIG. 29 is a functional block diagram of yet another exemplary femtonode, such as femto node 1710 in FIG. 17. As shown, the femto node 2900may comprise a processing module 2905, a storing module 2910, aformatting module 2915, a mapping module 2920, a generating module 2925,a receiving module 2940, a transmitting module 2941, a communicationsmodule 2945, a transferring module 2950, an assigning module 2960, andan obtaining module 2970. The processing module 2905 may correspond atleast in some aspects to, for example, a processor as discussed herein.The storing module 2910 may correspond at least in some aspects to, forexample, a memory as discussed herein. The formatting module 2915 maycorrespond at least in some aspects to, for example, a message formatteras discussed herein. The mapping module 2920 may correspond at least insome aspects to, for example, a processor as discussed herein. Thegenerating module 2925 may correspond at least in some aspects to, forexample, a processor as discussed herein. In an aspect, the generatingmodule 2925 may comprise one or more of an obtaining module (not shown)and a creating module (not shown). The obtaining module may correspondat least in some aspects to, for example, a message interpreter asdiscussed herein. The creating module may correspond at least in someaspects to, for example, a message formatter as discussed herein. Thereceiving module 2940 may correspond at least in some aspects to, forexample, a wired or wireless network interface as discussed herein. Thetransmitting module 2941 may correspond at least in some aspects to, forexample, a wired or wireless network interface as discussed herein. Thecommunications module 2945 may correspond at least in some aspects to,for example, a processor as discussed herein. The transferring module2950 may correspond at least in some aspects to, for example, a wired orwireless network interface as discussed herein. The assigning module2960 may correspond at least in some aspects to, for example, a messageformatter as discussed herein. The obtaining module 2970 may correspondat least in some aspects to, for example, a message interpreter asdiscussed herein.

FIG. 30 is a functional block diagram of yet another exemplary proxy,such as proxy 2170 in FIG. 21. As shown, the proxy 3000 may comprise aprocessing module 3005, a storing module 3010, a formatting module 3015,a maintaining module 3020, a partitioning module 3025, a receivingmodule 3040, a transmitting module 3041, a communications module 3045, adetermining module 3050, a modifying module 3060, and an obtainingmodule 3070. The processing module 3005 may correspond at least in someaspects to, for example, a processor as discussed herein. The storingmodule 3010 may correspond at least in some aspects to, for example, amemory as discussed herein. The formatting module 3015 may correspond atleast in some aspects to, for example, a message formatter as discussedherein. The maintaining module 3020 may correspond at least in someaspects to, for example, a processor as discussed herein. Thepartitioning module 3025 may correspond at least in some aspects to, forexample, a processor as discussed herein. In an aspect, the partitioningmodule 3025 may comprise an allocating module (not shown). Theallocating module may correspond at least in some aspects to, forexample, a processor as discussed herein. The receiving module 3040 maycorrespond at least in some aspects to, for example, a wired or wirelessnetwork interface as discussed herein. The transmitting module 3041 maycorrespond at least in some aspects to, for example, a wired or wirelessnetwork interface as discussed herein. In an aspect, the transmittingmodule 3041 may comprise a spoofing module (not shown). The spoofingmodule may correspond at least in some aspects, for example, to aprocessor as discussed herein. The communications module 3045 maycorrespond at least in some aspects to, for example, a processor asdiscussed herein. The determining module 3050 may correspond at least insome aspects to, for example, a processor as discussed herein. Themodifying module 3060 may correspond at least in some aspects to, forexample, a message formatter as discussed herein. The obtaining module3070 may correspond at least in some aspects to, for example, a messageinterpreter as discussed herein. In an aspect, the obtaining module 3070may comprise one or more of a mapping module (not shown) and a combiningmodule (not shown). The mapping module may correspond at least in someaspects to, for example, a processor as discussed herein. The combiningmodule may correspond at least in some aspects to, for example, aprocessor as discussed herein.

FIG. 31 is a functional block diagram of yet another exemplary macronode, such as macro node 2110 in FIG. 21. As shown, the macro node 3100may comprise a processing module 3105, a storing module 3110, aformatting module 3115, a receiving module 3140, a transmitting module3141, a communications module 3145, a determining module 3150, and anobtaining module 3170. The processing module 3105 may correspond atleast in some aspects to, for example, a processor as discussed herein.The storing module 3110 may correspond at least in some aspects to, forexample, a memory as discussed herein. The formatting module 3115 maycorrespond at least in some aspects to, for example, a message formatteras discussed herein. The receiving module 3140 may correspond at leastin some aspects to, for example, a wired or wireless network interfaceas discussed herein. The transmitting module 3141 may correspond atleast in some aspects to, for example, a wired or wireless networkinterface as discussed herein. The communications module 3145 maycorrespond at least in some aspects to, for example, a processor asdiscussed herein. The determining module 3150 may correspond at least insome aspects to, for example, a processor as discussed herein. Theobtaining module 3170 may correspond at least in some aspects to, forexample, a message interpreter as discussed herein.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an example of exemplary approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged while remainingwithin the scope of the present disclosure. The accompanying methodclaims present elements of the various steps in a sample order, and arenot meant to be limited to the specific order or hierarchy presented.

The embodiments presented herein and other embodiments are furtherdescribed in greater detail in Provisional Application No. 61/152,589entitled “High Rate Packet Data (HRPD) Idle State Handout From Femto toMacro Access Network” filed Feb. 13, 2009, expressly incorporated byreference herein. While the specification describes particular examplesof the present invention, those of ordinary skill can devise variationsof the present invention without departing from the inventive concept.For example, the teachings herein may refer to packet-switched domainnetwork elements but are equally applicable to circuit-switched networkelements.

Those skilled in the art will understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those skilled in the art will further appreciate that the variousillustrative logical blocks, modules, circuits, methods and algorithmsdescribed in connection with the examples disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,methods and algorithms have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The various illustrative logical blocks, modules, and circuits describedin connection with the examples disclosed herein may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The methods or algorithms described in connection with the examplesdisclosed herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. A storagemedium may be coupled to the processor such that the processor can readinformation from, and write information to, the storage medium. In thealternative, the storage medium may be integral to the processor. Theprocessor and the storage medium may reside in an ASIC.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. by way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes compact disc (CD), laser disc,optical disc, digital versatile disc (DVD), floppy disk and blu-ray discwhere disks usually reproduce data magnetically, while discs reproducedata optically with lasers. Combinations of the above should also beincluded within the scope of computer-readable media.

The previous description of the disclosed examples is provided to enableany person skilled in the art to make or use the present invention.Various modifications to these examples will be readily apparent tothose skilled in the art, and the generic principles defined herein maybe applied to other examples without departing from the spirit or scopeof the invention. Thus, the present invention is not intended to belimited to the examples shown herein but is to be accorded the widestscope consistent with the principles and novel features disclosedherein.

1. A method of identifying an address comprising: receiving a first andsecond identifier from an access terminal; generating a domain namebased, at least in part, upon the first and second identifiers;transmitting a domain name server query using the domain name; andreceiving the address of a source access node in response to the domainname server query.
 2. The method of claim 1, wherein the firstidentifier comprises a color code.
 3. The method of claim 1, wherein thecolor code is 8 bits long.
 4. The method of claim 1, wherein the firstidentifier comprises one or more bits from an upper unicast accessterminal identifier.
 5. The method of claim 4, wherein the firstidentifier comprises a portion of the most significant bits from acombined unicast access terminal identifier.
 6. The method of claim 2,wherein the second identifier comprises one or more bits from a lowerunicast access terminal identifier.
 7. The method of claim 6, whereinthe second identifier comprises a portion of the least significant bitsfrom a combined unicast access terminal identifier.
 8. The method ofclaim 2, further comprising mapping the color code to one or more bitsof an upper unicast access terminal identifier.
 9. The method of claim8, wherein generating the domain name comprises: obtaining an operatordomain string; obtaining a subnet identifier; creating a firstsub-domain string based at least in part on the subnet identifier;creating a second sub-domain string based at least in part on one ormore of the least significant bits of the upper unicast access terminalidentifier in combination with one or more bits of the lower unicastaccess terminal identifier; and creating a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 10. The method ofclaim 8, wherein generating the domain name comprises: obtaining anoperator domain string; and creating a domain name string based at leastin part on one or more of the operator domain string, the upper unicastaccess terminal identifier, and the lower unicast access terminalidentifier.
 11. The method of claim 1, wherein the source access nodecomprises a femto access node.
 12. The method of claim 1, furthercomprising transferring a data session from the source access node. 13.A method of registering an address comprising: assigning a first andsecond identifier to an access terminal; generating a domain name based,at least in part, upon the first and second identifiers; obtaining theaddress of a source access node; and transmitting a domain name serverregistration using the domain name and the address of the source accessnode.
 14. The method of claim 13, wherein the first identifier comprisesa color code.
 15. The method of claim 14, wherein the color code is 8bits long.
 16. The method of claim 13, wherein the first identifiercomprises one or more bits from an upper unicast access terminalidentifier.
 17. The method of claim 16, wherein the first identifiercomprises a portion of the most significant bits from a combined unicastaccess terminal identifier.
 18. The method of claim 13, wherein thesecond identifier comprises one or more bits from a lower unicast accessterminal identifier.
 19. The method of claim 18, wherein the secondidentifier comprises a portion of the least significant bits from acombined unicast access terminal identifier.
 20. The method of claim 14,further comprising mapping the color code to one or more bits of anupper unicast access terminal identifier.
 21. The method of claim 20,wherein generating the domain name comprises: obtaining an operatordomain string; obtaining a subnet identifier; creating a firstsub-domain string based at least in part on the subnet identifier;creating a second sub-domain string based at least in part on one ormore of the least significant bits of the upper unicast access terminalidentifier in combination with one or more bits of the lower unicastaccess terminal identifier; and creating a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 22. The method ofclaim 20, wherein generating the domain name comprises: obtaining anoperator domain string; and creating a domain name string based at leastin part on one or more of the operator domain string, the upper unicastaccess terminal identifier, and the lower unicast access terminalidentifier.
 23. The method of claim 13, wherein the source access nodecomprises a femto access node.
 24. An apparatus capable of identifyingan address comprising: a processor configured to: receive a first andsecond identifier from an access terminal; generate a domain name based,at least in part, upon the first and second identifiers; transmit adomain name server query using the domain name; and receive the addressof a source access node in response to the domain name server query. 25.The apparatus of claim 24, wherein the first identifier comprises acolor code.
 26. The apparatus of claim 25, wherein the color code is 8bits long.
 27. The apparatus of claim 24, wherein the first identifiercomprises one or more bits from an upper unicast access terminalidentifier.
 28. The apparatus of claim 27, wherein the first identifiercomprises a portion of the most significant bits from a combined unicastaccess terminal identifier.
 29. The apparatus of claim 24, wherein thesecond identifier comprises one or more bits from a lower unicast accessterminal identifier.
 30. The apparatus of claim 29, wherein the secondidentifier comprises a portion of the least significant bits from acombined unicast access terminal identifier.
 31. The apparatus of claim25, wherein the processor is further configured to map the color code toone or more bits of an upper unicast access terminal identifier.
 32. Theapparatus of claim 31, wherein the processor is further configured to:obtain an operator domain string; obtain a subnet identifier; create afirst sub-domain string based at least in part on the subnet identifier;create a second sub-domain string based at least in part on one or moreof the least significant bits of the upper unicast access terminalidentifier in combination with one or more bits of the lower unicastaccess terminal identifier; and create a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 33. The apparatusof claim 31, wherein the processor is further configured to: obtain anoperator domain string; and create a domain name string based at leastin part on one or more of the operator domain string, the upper unicastaccess terminal identifier, and the lower unicast access terminalidentifier.
 34. The apparatus of claim 24, wherein the source accessnode comprises a femto access node.
 35. The apparatus of claim 24,wherein the processor is further configured to transfer a data sessionfrom the source access node.
 36. An apparatus capable of registering anaddress comprising: a processor configured to: assign a first and secondidentifier to an access terminal; generate a domain name based, at leastin part, upon the first and second identifiers; obtain the address of asource access node; and transmit a domain name server registration usingthe domain name and the address of the source access node.
 37. Theapparatus of claim 36, wherein the first identifier comprises a colorcode.
 38. The apparatus of claim 37, wherein the color code is 8 bitslong.
 39. The apparatus of claim 36, wherein the first identifiercomprises one or more bits from an upper unicast access terminalidentifier.
 40. The apparatus of claim 39, wherein the first identifiercomprises a portion of the most significant bits from a combined unicastaccess terminal identifier.
 41. The apparatus of claim 36, wherein thesecond identifier comprises one or more bits from a lower unicast accessterminal identifier.
 42. The apparatus of claim 41, wherein the secondidentifier comprises a portion of the least significant bits from acombined unicast access terminal identifier.
 43. The apparatus of claim37, wherein the processor is further configured to map the color code toone or more bits of an upper unicast access terminal identifier.
 44. Theapparatus of claim 43, wherein the processor is further configured to:obtain an operator domain string; obtain a subnet identifier; create afirst sub-domain string based at least in part on the subnet identifier;create a second sub-domain string based at least in part on one or moreof the least significant bits of the upper unicast access terminalidentifier in combination with one or more bits of the lower unicastaccess terminal identifier; and create a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 45. The apparatusof claim 43, wherein the processor is further configured to: obtain anoperator domain string; and create a domain name string based at leastin part on one or more of the operator domain string, the upper unicastaccess terminal identifier, and the lower unicast access terminalidentifier.
 46. The apparatus of claim 36, wherein the source accessnode comprises a femto access node.
 47. An apparatus capable ofidentifying an address comprising: means for receiving a first andsecond identifier from an access terminal; means for generating a domainname based, at least in part, upon the first and second identifiers;means for transmitting a domain name server query using the domain name;and means for receiving the address of a source access node in responseto the domain name server query.
 48. The apparatus of claim 47, whereinthe first identifier comprises one or more bits from an upper unicastaccess terminal identifier.
 49. The apparatus of claim 47, wherein thesecond identifier comprises one or more bits from a lower unicast accessterminal identifier.
 50. The apparatus of claim 47, further comprisingmeans for mapping a color code to one or more bits of an upper unicastaccess terminal identifier.
 51. The apparatus of claim 50, wherein themeans for generating the domain name comprises: means for obtaining anoperator domain string; means for obtaining a subnet identifier; meansfor creating a first sub-domain string based at least in part on thesubnet identifier; means for creating a second sub-domain string basedat least in part on one or more of the least significant bits of theupper unicast access terminal identifier in combination with one or morebits of the lower unicast access terminal identifier; and means forcreating a domain name string based at least in part on one or more ofthe operator domain string, the first sub-domain string, and the secondsub-domain string.
 52. The apparatus of claim 50, wherein the means forgenerating a domain name comprises: means for obtaining an operatordomain string; and means for creating a domain name string based atleast in part on one or more of the operator domain string, the upperunicast access terminal identifier, and the lower unicast accessterminal identifier.
 53. The apparatus of claim 47, wherein the sourceaccess node comprises a femto access node.
 54. The apparatus of claim47, further comprising means for transferring a data session from thesource access node.
 55. An apparatus capable of registering an addresscomprising: means for assigning a first and second identifier to anaccess terminal; means for generating a domain name based, at least inpart, upon the first and second identifiers; means for obtaining theaddress of a source access node; and means for transmitting a domainname server registration using the domain name and the address of thesource access node.
 56. The apparatus of claim 55, wherein the firstidentifier comprises one or more bits from an upper unicast accessterminal identifier.
 57. The apparatus of claim 55, wherein the secondidentifier comprises one or more bits from a lower unicast accessterminal identifier.
 58. The apparatus of claim 55, further comprisingmeans for mapping a color code to one or more bits of an upper unicastaccess terminal identifier.
 59. The apparatus of claim 58, wherein themeans for generating the domain name comprises: means for obtaining anoperator domain string; means for obtaining a subnet identifier; meansfor creating a first sub-domain string based at least in part on thesubnet identifier; means for creating a second sub-domain string basedat least in part on one or more of the least significant bits of theupper unicast access terminal identifier in combination with one or morebits of the lower unicast access terminal identifier; and means forcreating a domain name string based at least in part on one or more ofthe operator domain string, the first sub-domain string, and the secondsub-domain string.
 60. The apparatus of claim 58, wherein the means forgenerating a domain name comprises: means for obtaining an operatordomain string; and means for creating a domain name string based atleast in part on one or more of the operator domain string, the upperunicast access terminal identifier, and the lower unicast accessterminal identifier.
 61. The apparatus of claim 55, wherein the sourceaccess node comprises a femto access node.
 62. The apparatus of claim55, further comprising means for transferring a data session from thesource access node.
 63. A computer program product comprising: acomputer readable medium comprising: code capable of causing at leastone computer to receive a first and second identifier from an accessterminal; code capable of causing at least one computer to generate adomain name based, at least in part, upon the first and secondidentifiers; code capable of causing at least one computer to transmit adomain name server query using the domain name; and code capable ofcausing at least one computer to receive the address of a source accessnode in response to the domain name server query.
 64. The computerprogram product of claim 63, wherein the first identifier comprises oneor more bits from an upper unicast access terminal identifier.
 65. Thecomputer program product of claim 63, wherein the second identifiercomprises one or more bits from a lower unicast access terminalidentifier.
 66. The computer program product of claim 63, wherein thecomputer readable medium further comprises code capable of causing atleast one computer to map a color code to one or more bits of an upperunicast access terminal identifier.
 67. The computer program product ofclaim 66, wherein the code capable of causing at least one computer togenerate a domain name comprises: code capable of causing at least onecomputer to obtain an operator domain string; code capable of causing atleast one computer to obtain a subnet identifier; code capable ofcausing at least one computer to create a first sub-domain string basedat least in part on the subnet identifier; code capable of causing atleast one computer to create a second sub-domain string based at leastin part on one or more of the least significant bits of the upperunicast access terminal identifier in combination with one or more bitsof the lower unicast access terminal identifier; and code capable ofcausing at least one computer to create a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 68. The computerprogram product of claim 66, wherein the code capable of causing atleast one computer to generate a domain name comprises: code capable ofcausing at least one computer to obtain an operator domain string; andcode capable of causing at least one computer to create a domain namestring based at least in part on one or more of the operator domainstring, the upper unicast access terminal identifier, and the lowerunicast access terminal identifier.
 69. The computer program product ofclaim 63, wherein the source access node comprises a femto access node.70. The computer program product of claim 63, further comprising codecapable of causing at least one computer to transfer a data session fromthe source access node.
 71. A computer program product comprising: acomputer readable medium comprising: code capable of causing at leastone computer to assign a first and second identifier to an accessterminal; code capable of causing at least one computer to generate adomain name based, at least in part, upon the first and secondidentifiers; code capable of causing at least one computer to obtain theaddress of a source access node; and code capable of causing at leastone computer to transmit a domain name server registration using thedomain name and the address of the source access node.
 72. The computerprogram product of claim 71, wherein the first identifier comprises oneor more bits from an upper unicast access terminal identifier.
 73. Thecomputer program product of claim 71, wherein the second identifiercomprises one or more bits from a lower unicast access terminalidentifier.
 74. The computer program product of claim 71, wherein thecomputer readable medium further comprises code capable of causing atleast one computer to map a color code to one or more bits of an upperunicast access terminal identifier.
 75. The computer program product ofclaim 74, wherein the code capable of causing at least one computer togenerate a domain name comprises: code capable of causing at least onecomputer to obtain an operator domain string; code capable of causing atleast one computer to obtain a subnet identifier; code capable ofcausing at least one computer to create a first sub-domain string basedat least in part on the subnet identifier; code capable of causing atleast one computer to create a second sub-domain string based at leastin part on one or more of the least significant bits of the upperunicast access terminal identifier in combination with one or more bitsof the lower unicast access terminal identifier; and code capable ofcausing at least one computer to create a domain name string based atleast in part on one or more of the operator domain string, the firstsub-domain string, and the second sub-domain string.
 76. The computerprogram product of claim 74, wherein the code capable of causing atleast one computer to generate a domain name comprises: code capable ofcausing at least one computer to obtain an operator domain string; andcode capable of causing at least one computer to create a domain namestring based at least in part on one or more of the operator domainstring, the upper unicast access terminal identifier, and the lowerunicast access terminal identifier.
 77. The computer program product ofclaim 71, wherein the source access node comprises a femto access node.